Uwe Brauer writes:
Thanks for replying, even though you already solved this a different
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x25)
control Control_L (0x42), Control_R (0x69)
mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
This is very wrong, at least in an Xmodmap world. I don't know about
XKB -- it permits a number of behaviors that were illegal or undefined
in the old keymap scheme, but I never figured out what was going on --
the docs are horrible.
mod2 Num_Lock (0x4d)
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
This too. The problem is that all of the keys in a modifier map
*must* represent the same "shift". The interpretation here is not the
same as the 8 possible keysyms in a keycode statement.
I don't know what would happen here, it's undefined behavior. I
suspect that XEmacs will pick up Alt on mod1 and Super on mod4.
XEmacs tends to treat Alt as Meta unless both are defined, which is
why XEmacs recognizes Meta but not Hyper.
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
I don't know if this is OK or not. I *think* those are actually
different names for the same thing, so it's OK, but I'm not sure.
However I *solved my problem*, by sorting out the modifier mess, in
message I wrote 8th of march but which ended up in a slightly different
Yeah, I saw that. Congratulations!
XEmacs-Beta mailing list