Josip Gracin wrote:
> You have mod1 associated with both Alt and Meta, and mod4
associated
> with both Super and Hyper. This won't work, as XEmacs cannot figure
> out which modifiers the mod1 and mod3 bits are supposed to represent.
> It normally generates a warning about this situation.
Interesting. The mapping that I have is the default in Ubuntu/Gnome,
and XEmacs somehow manages to grok it without issuing any warnings.
Anyway, this is my current mapping.
shift Shift_L (0x32), Shift_R (0x3e)
lock
control Control_L (0x25), Control_L (0x42), Control_R (0x6d)
mod1 Alt_L (0x40), Alt_L (0x7d), Meta_L (0x9c)
mod2 Num_Lock (0x4d)
mod3 Super_L (0x73), Super_L (0x7f)
mod4 Hyper_L (0x80)
mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x71),
ISO_Level3_Shift (0x7c)
Is XEmacs treating Alt as being the same as Meta?
Probably. If pressing Alt+X brings up a M-x prompt, then it's treating
mod1 as Meta.
I have both:
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1 Alt_L (0x73), Alt_L (0x7f)
mod2 Num_Lock (0x4d)
mod3
mod4 Meta_L (0x40), Meta_L (0x7d), Meta_L (0x9c)
mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x7c)
[From the keycodes, you can see that the "Windows" keys are Alt_*
while the "Alt" keys are Meta_*.]
If I press Windows+X (i.e. Alt-x), I get "A-x not defined." in the
echo area; Alt+X (i.e. Meta-x) gives me the M-x prompt.
I have Alt rather than Meta on mod1 so that I can use Alt-<key> for WM
shortcuts without shadowing any of XEmacs' Meta-<key> bindings. E.g.
Alt-Tab switches between windows, while Meta-Tab does completion
within XEmacs.
--
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta