On Mon, Feb 23, 2004 at 12:23:05PM +0100, Roland Hautz wrote: > On Mon, 23 Feb 2004, Dominik Vogt wrote: > > > I don't think so. Run > > > > $ xmodmap -pm > > ~>xmodmap -pm > xmodmap: up to 3 keys per modifier, (keycodes in parentheses): > > shift Shift_L (0x32), Shift_R (0x3e) > lock Caps_Lock (0x42) > control Control_L (0x25), Control_R (0x6d) > mod1 Alt_L (0x40), BadKey (0x7d), BadKey (0x9c) > mod2 Num_Lock (0x4d) > mod3 > mod4 Super_L (0x73), BadKey (0x7f), Super_R (0x74) > mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x7c) > > > and > > > > $ xmodmap -pke > > ~>xmodmap -pke | egrep '(Alt)|(Meta)|(Shift)' > keycode 50 = Shift_L > keycode 62 = Shift_R > keycode 64 = Alt_L Meta_L > keycode 113 = ISO_Level3_Shift Multi_key > keycode 124 = ISO_Level3_Shift > keycode 125 = NoSymbol Alt_L > keycode 156 = NoSymbol Meta_L > > > . This displays which modifiers are defined and which keys > > generate them. The Shift_... or Alt_... key is probably > > configured in an odd way. > > OK, shift+alt is producing Meta_L. But I expected applications including > fvwm would interpret Alt and Meta as synonyms?
Yes, it does. Your problem occurs because fvwm can not decide whether it should have expected Shift pressed for the Alt_L key or not. To understand the problem, consider this: Some keyboards map Shift-F1 to F11. Now, what does this binding mean? Key F11 A S something Does this apply to Shift-F1? Unfortunately it's not possible to find out exactly which key was pressed with which modifiers held, so all you can do is guess. In fvwm, I decided to ignore the "S" in this binding and treat it exactly like Key F1 A S something Key F11 S something This can have some funny results in some exotic cases like yours. I'd like to fix it, but doing so will inadvertedly break other cases. Ciao Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
