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