>>>> "MB" == Martin Buchholz <of Thu, 18 Jan
2001 16:20:29 +0900> writes:
>>>> "Michael" == Michael Kifer
Michael> I have a habit of making the useless caps lock key to act as
Michael> control key, which I do in .Xmodmap. I also do things with Alt_R
Michael> and such. When XEmacs starts up, it gives me a mouthful. Why
Michael> does it care?
MB> What you are doing is not ICCCM-compliant, I believe.
MB> You have to have one of the Control keys generate control.
Why? I have already assigned control to caps lock. I don't have keys to waste.
I actually bind the ctl key (on the PC eyboard) to save-some-buffers !
MB> You want to do something like this: (editing required)
MB> xmodmap \
MB> -e 'clear lock' \
MB> -e 'clear control' \
MB> -e 'keycode 126 = Control_L' \
MB> -e 'add control = Control_L' \
MB> -e 'add control = Control_R' # if you have a Control_R key
I do something similar:
remove Control = Control_L
remove Lock = Caps_Lock
keysym Control_R = Caps_Lock
add Control = Caps_Lock
keycode 37 = F22
It is probably the last line that causes the warnings: I make this key look
like F22 and then bind F22 to save-some-buffers.
MB> and what you're doing typically works even though it's illegal,
I think it should be illegal to sell keyboards that have Control in the
wrong place :-)
MB> so maybe we should turn the warning off.
Please do. Why should you care how the keys are mapped? Chances are that if
I did something with the keys that can seriously break XEmacs, other
editors won't work as well (e.g., vi).