New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User data for awful.key cannot be shared #1401
Comments
So, something somewhere is modifying a table that it is not supposed to modify? Or using a table as a key in another table where it shouldn't? |
It should clone the table from 'data' arg instead of just assigning it
I already have some fix in mind, but will write it after will manage with
the tests as planned
…On Tue, 17 Jan 2017 at 21:04, Uli Schlachter ***@***.***> wrote:
So, something somewhere is modifying a table that it is not supposed to
modify? Or using a table as a key in another table where it shouldn't?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#1401 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABlDdRCxJXo2hTAdK60xCe6NG9UbynpXks5rTR7lgaJpZM4Lj22j>
.
|
Thanks a lot! |
actionless
added a commit
to actionless/awesome
that referenced
this issue
Jan 30, 2017
actionless
added a commit
to actionless/awesome
that referenced
this issue
Jan 30, 2017
closes awesomeWM#1401 fix(tests: awesomerc): use `awful.key.execute` instead of local helper function
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Output of
awesome --version
:How to reproduce the issue:
Somewhere in your config where you define keys, replace a local table with description/group with a variable that contains this table. Use the same variable in some other key.
E.g.
Restart with the new config, open hotkeys popup.
Actual result:
Expected result:
There should have been two records for different keys with the same description/group. Or at least there should be a documentation notice on
awful.key
that you can't reusedata
argument.The text was updated successfully, but these errors were encountered: