At FOSDEM I was hacking a little on a script called Quicktile which seems to be a handy tool for window placement. More on that later, but one of the things that makes it useful is that you can have it listen to certain key combos and react on them for window placement.
Except that, both on my T61 Lenovo laptop and my Logitech Wave keyboard, the shortcuts you’re supposed to use (Ctrl-Alt-Keypad numbers) don’t actually work.
Since I’ve always been scared about the way keyboards are handled in Linux I never took the time to learn and am now thoroughly confused by all the layers involved. Raw, cooked, kernel, console, X, xcb, keyboard mappings, …
So, simple question to all you knowledgeable hackers – if my Gnome Keyboard Shortcuts preferences applet behaves like this, in combination with ctrl-alt:
- 1-2-3-4-6-7-8-9 are dead
- 5 and 0 act like Escape (abort)
- Enter is correctly recognized as KP Enter
- All others (., /, *, -, +) are dead too
– then what is wrong, what should I reconfigure, or what should I do to get all my keypad keys recognized ?
Interestingly, my Thinkpad behaves much the same, except that it lacks a Keypad Enter, but the main Enter button is recognized as a KP Enter.
UPDATE: Jan pointed me in the right direction apparently this is due to the mousekeys function, which hijacks your numeric keypad to let you move the mouse pointer using the keyboard.
I had no idea this existed, and I honestly still don’t know if I should be feeling mentally violated for having my interpretation of NumLock thus subverted, or whether I just discovered a supercool feature that would have helped me out in so many cases in the past where the mouse for some reason didn’t work. Ah, the agony of having choice!
I’ll try it out on my Thinkpad tomorrow.