key mapping in Xmodmap

The following has been an annoyance for a while, but now I decided to speak up :-) I have a habit of making the useless caps lock key to act as control key, which I do in .Xmodmap. I also do things with Alt_R and such. When XEmacs starts up, it gives me a mouthful. Why does it care? Especially the last two warnings look silly in view of the fact that it is precisely my intention that capslock would generate modcontrol (and that the way to do this is in the X windows FAQ). --michael (1) (key-mapping/warning) The meanings of the modifier bits Mod1 through Mod5 are determined by the keysyms used to control those bits. Mod1 does NOT always mean Meta, although some non-ICCCM-compliant programs assume that. (2) (key-mapping/warning) The semantics of the modifier bits ModShift, ModLock, and ModControl are predefined. It does not make sense to assign ModControl to any keysym other than Control_L or Control_R, or to assign any modifier bits to the "control" keysyms other than ModControl. You can't turn a "control" key into a "meta" key (or vice versa) by simply assigning the key a different modifier bit. You must also make that key generate an appropriate keysym (Control_L, Meta_L, etc). (3) (key-mapping/warning) XEmacs: Caps_Lock (0x6d) generates ModControl, which is nonsensical. (4) (key-mapping/warning) XEmacs: Caps_Lock (0x42) generates ModControl, which is nonsensical.