Re: xmodmap, Caps Lock, super hyper

Uwe Brauer writes: Thanks for replying, even though you already solved this a different way. 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. 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. 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. Yeah, I saw that. Congratulations! _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta