If you are trying to set up keyboard shortcuts in Window Maker and you find yourself getting some really strange output in the Preferences Menu panel, it could be that your "num lock" is engaged. Apparently, this is something that has been an issue for a long time, but I just found out about it the hard way.
Here's the result of doing a key capture with "num lock" on on my desktop system (I'm trying to bind Mod4 - the infamous "windows" key - plus "w" to Firefox):
And here is the result with "num lock" off:
And yes, the shortcut works just fine after saving it in WPrefs.app.
So if you see weird, unexpected output while capturing a keybind in Window Maker - check "num lock."


Caps lock is a pain so I disable it completely.
ReplyDeleteIn ~/GNUstep/Library/WindowMaker/autostart I have:
/usr/bin/xmodmap -e "clear Lock"
No more caps lock and it's not missed at all.
Dear busprof,
DeleteProbably, it is a out-tipic question. However, I haven't found anything more related than this post to state my question. At the Keyboard Shortcut Preferences menu actions, I'm trying to configure the "Open applications menu" with the Mod4 key (window key); nevertheless, there is no change and I am still using the F12 key to pop this menu.
I really appreciate any help you can provide,
A random linux user
Anonymous
ReplyDeleteI just tried changing my own shortcut to Mod4, with no luck using the "capture" dialog in the Shortcut Preferences tool. At least this confirms the same behavior that you are seeing. I have a "menu" key on my Lenovo keyboard and I was able to use it as the shortcut instead of F12, so I am not sure why Mod4 is not recognized - can only confirm that it is not.
If I come up with a method for using the Mod4 key to open the applications menu I will post it here.