In the default example configuration for xbindkeys, there is an example of specifying keycodes directly:
# set directly keycode (here control + f with my keyboard) #"xterm" # c:41 + m:0x4
What do the c:
and m:
mean? The documentation for xbindkeys does not shed any light on this.
Also, I know you can use xbindkeys -k
to find the codes for a key. If that does not work (for one of the nonstandard fn keys, the command does not respond to the keypress and it instead does its normal action), does that mean that xbindkeys
cannot handle that key? Even if I know the keycode from showkey -k
(217 in my case)?
gnome-control-center
), which then letxbindkeys -k
pick it up. Seems it wasm:0x10 + c:255
, so the key code was indeed off by 8. Not sure why it'sm:0x10
though. – nog642 Mar 14 '24 at 13:21m:0x10 + c:255
won't trigger if NumLock is off? I've noticed that all the letters by themselves also have them:0x10
modifier. I mean this laptop keyboard doesn't have a NumLock key anyway, but if this were on a desktop, it would be weird if the letter "a" with NumLock on and the letter "a" without NumLock off were considered different. – nog642 Mar 15 '24 at 04:54