Dominik Vogt writes:
> Most likely the '4' modifier isn't properly bound in X. What is the output
> of 'xmodmap -pm'? Is there a '4' modifier at all? Is is bound to the key
> you would expect?
xmodmap -pm gives:
xmodmap: up to 2 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), Alt_R (0x71)
mod2 Num_Lock (0x4d), Hyper_L (0x73)
mod3 Super_L (0x75)
mod4 Pause (0x6e)
mod5 Scroll_Lock (0x4e), Print (0x6f)
So, mod4 is bound to something, and yes it is the key I would
suspect. However, I don't think this is FVWM's fault now (I suspected it
wasn't, but mailed this list to make sure). My set of keybindings with the
`4' modifier work properly with the NumLock (!) on. My set of keybindings
with the `5' modifier work properly with the NumLock off (as they
should). So I think my X server is _very_ buggy. Thanks for the help. Any
suggestions on how to work around a buggy X server?
--
Nathan | froydnj_at_rose-hulman.edu | http://www.rose-hulman.edu/~froydnj/
Evolution is a million line computer program falling into place by accident.
--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Aug 04 1999 - 22:03:48 BST