-
Notifications
You must be signed in to change notification settings - Fork 598
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
Redone: Fix for Issue 2527 #2580
Conversation
* Update awesomerc.lua * Update init.lua (#6)
* Update init.lua Add return values to allow for a fallback theme in the case of an error Ensured debug messages are printed Fixed table option Improved error handling testing... local code, err, file = nil, nil, nil code, err = beautiful.myinit( file ) -- empty variable will fail > 2019-01-11 14:23:54 E: beautiful: error loading theme: no theme specified code, err = beautiful.myinit( path_this .. "themes/shelby/bad.lua" ) -- file that loadfile says is ok but dofile errors on > 2019-01-11 14:23:54 E: beautiful: error loading theme: /home/david/.config/awesome/themes/shelby/bad.lua > 2019-01-11 14:23:54 E: theme file error: /home/david/.config/awesome/themes/shelby/bad.lua:17: attempt to index a nil value (global 'beautiful') code, err = beautiful.myinit( function() end ) -- Should not do anything with this > 2019-01-11 14:23:54 E: beautiful: error loading theme: function: 0x55f6006795f0 > 2019-01-11 14:23:54 E: theme file error: nil code, err = beautiful.myinit( {} ) -- Same as not providing a file 2019-01-11 14:23:54 E: beautiful: error loading theme: table: 0x55f600679770 2019-01-11 14:23:54 E: theme file error: nil code, err = beautiful.myinit( path_this .. "themes/shelby/theme.lua" ) -- A valid file >
* Update luaa.c Required code changes Test cases... startx [exec awesome] user's rc.lua xdg/awesome/rc.lua startx [exec awesome -c <name>] '/home/user/.config/awesome/xyz.lua' '/home/user/xyz.lua' Xephyr [in build directory] DISPLAY=:1 ./awesome -c awesomerc.lua Made config_path conform to style of themes_path and icon_path (ie: removed the final '/')
Fixing Travis warning
Codecov Report
@@ Coverage Diff @@
## master #2580 +/- ##
==========================================
+ Coverage 84.66% 84.68% +0.01%
==========================================
Files 496 496
Lines 33738 33762 +24
==========================================
+ Hits 28563 28590 +27
+ Misses 5175 5172 -3
|
Confirming local development git is up to date and has no other changes...
|
Confirming changes are the same...
|
Confirming changes are the same...
|
Confirming running build versiion with modified awesomerc.lua...
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i've already explained to you what changing hotkeys_popup to add function which makes sense only in context of using it as callback in menu won't be welcome
please redo it normally
and second question: how do you know it's fixing multi-screen issue if you told in another ticket what you don't have env to test it? |
Second question first... I have a dual head system but it is running 4.2 and I used Xephyr to test the mods, but I only have that working with one display I did actually mention that I found a way to test it in the 'Issue' - "I cloned my user and set it up so startx runs /_testing/awesome/build/awesome" Here's a more detailed explanation... I cloned my user and set it up so startx runs /_testing/awesome/build/awesome I'm now able to login as 'clone' on a separate tty 'and simply startx running the build version All this can be see in the 4 testing comments I posted with this PR...
|
While I didn't understand you saying that, it works in any context (ie: the following will also work)...
The difference between the two is that |
but it drops first argument specifically for compatibility with being used as menu callback |
instead i recommend you adding optional argument to function show_help to define that behavior explicitly (in the same style like its behavior is altered by |
That is far from the case - The menu callback behaviour only occurs when the function call is done without brackets In short, the menu compatibility comes from the new 'show' function not having any arguments, so whatever the menu passes goes nowhere The reason I pass nil as the first argument is because the client isn't a factor. In fact, if no client is currently in focus on the current screen but one is in focus on the other screen (the error case that I am fixing) the existing code
|
Note: Comment above was updated for greater accuracy and clarity |
anyway the described problem should be solved by creating new optional arg, not new function wrapper |
Why add that sort of complexity? The wrapper is IMHO quite elegant, aligns with the existing one in init.lua and allows a very neat rc.lua |
Damn - Github merged my fork - I will close this and redo |
Fix for hotkey_popup via awful menu showing on wrong screen
#2527
Next comments will show local testing and confirmation