You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first (and the third) binding won't work. However, for normal keybindings it's the other way around, the key must be specified in lower case, otherwise it won't work.
Note that it's the same case if you add Mod4 as modifier. However, adding Control (or both Mod4+Control) as modifier makes the keygrabber behave like the global keybindings.
Those should probably be consistent. I think the way the normal keybindings are set at the moment is more intuitive, i.e. keys should be specified in lower case. Is there some limitation outside of Awesome for this? Didn't look at that code yet.
The text was updated successfully, but these errors were encountered:
For shift this may seem obvious, but things like € are Alt-Gr + e for me and here it would be wrong to trat this as just e instead. So, I'm not really sure what the way to go here is. Perhaps just transform the resulting string to lowercase?
Is there some limitation outside of Awesome for this? Didn't look at that code yet.
The "normal keys" use just libxcb-keysyms and core-X11 protocol. The keygrabber code uses libxkbcommon and the XKB extension, thus do things "more properly". That's where the difference comes from, basically. (Feel free to search for bug reports saying that e.g. "this combination of keyboard layouts" causes problems; the reports say that the keyboard layout switch works fine in the prompt, but keybindings still use some other, old layout.)
When setting keybindings for a keygrabber with
Shift
as modifier, the key must be specified in upper case as well. Consider this example:The first (and the third) binding won't work. However, for normal keybindings it's the other way around, the key must be specified in lower case, otherwise it won't work.
Note that it's the same case if you add
Mod4
as modifier. However, addingControl
(or bothMod4+Control
) as modifier makes the keygrabber behave like the global keybindings.Those should probably be consistent. I think the way the normal keybindings are set at the moment is more intuitive, i.e. keys should be specified in lower case. Is there some limitation outside of Awesome for this? Didn't look at that code yet.
The text was updated successfully, but these errors were encountered: