Re: key mapping in Xmodmap

Michael> The following has been an annoyance for a while, but now I decided to speak Michael> up :-) Michael> I have a habit of making the useless caps lock key to act as control key, Michael> which I do in .Xmodmap. I also do things with Alt_R and such. Michael> When XEmacs starts up, it gives me a mouthful. Why does it Michael> care? What you are doing is not ICCCM-compliant, I believe. The ICCCM says: Convention Clients should determine the meaning of a modifier bit from the KeySyms being used to control it. which seems to mean that xemacs should interpret your xmodmapped capslock key with its _original_ meaning. You have to have one of the Control keys generate control. You want to do something like this: (editing required) xmodmap \ -e 'clear lock' \ -e 'clear control' \ -e 'keycode 126 = Control_L' \ -e 'add control = Control_L' \ -e 'add control = Control_R' # if you have a Control_R key But users typically don't figure this out, and what you're doing typically works even though it's illegal, so maybe we should turn the warning off. Has this been FAQized? If not, it should be.