Sid S <r03...@gmail.com> writes: > You should be using xmodmap OR xsetkbmap OR the configuration file, > not all three (though they shouldn't interfere with each other if > configured properly - they'd just all be doing the same thing).
It would be fine if they did what I want :) > If you wish to set Caps_Lock to be Control_L, you need to redefine > keycode 66, not 37 (37 is Control_L by default). Oh, thank you! You're right, I didn't change 66 when I made a new map for this particular keyboard --- not too surprising that things get messed up then. It seems to work now :) > You may also need to add "clear lock" or "clear Lock" before that > line. Sometimes it will or will not work if you don't do this and will > toggle Caps_Lock and press Control_L. Weird. Experiments with that quite some time ago yielded error messages. IIRC some bug was introduced somewhere so these options in the keymap didn't work anymore. Perhaps the bug has been fixed in the meantime, I don't know ... > Alternatively, you can use xsetkbmap like you described. Yes, I looked into that quite a while ago and found it's too complicated for changing a couple keys. That must have been when this bug with xmodmap came up and ctrl:nocaps became required in xorg.conf ... -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.