> > F1 and F2 do what F11 and F12 were bound too, irrespective of their own
> > bindings. F11 and F12 work as expected. I know the keymaps are ok because
> > I had ctwm doing the exact same config earlier today, so i know hitting
> > F1 really is sending and F1.
>
> I remember having similar problems with another machine:
>
> % xmodmap -display -pk | grep '(F1[12])'
> 95 0xffc8 (F11)
> 96 0xffc9 (F12)
>
> % xmodmap -display starlight:0 -pk | grep '(F1[12])'
> 67 0xffbe (F1) 0xffc8 (F11)
> 68 0xffbf (F2) 0xffc9 (F12)
> 95 0xffc8 (F11)
> 96 0xffc9 (F12)
>
> Unlike CTWM (I only guess about it), FVWM has a logic to bind the binding
>
> Key F11 A N Restart
>
> to all keycodes (67 and 95) that this keysym (F11) is assigned to.
>
> To fix this I would execute in ~/.xinirc:
>
> % xmodmap -e 'keycode 67 = F1' -e 'keycode 68 = F2'
>
> Or maybe just change the order of your "Key F1" and "Key F11" lines? :)
Thanks alot for that suggestion Mike. It works to switch the order
of the "Key" declarations, but it took me a little bit to straighten
out in my head exactly why. So I am posting the comment i added to
that section of my .fvwm2rc file, which explains explicitly why this
works.
# Note: why F11 and F12 *must* be bound before F1 and F2
#
# $ xmodmap -pk | grep '(F1[12])'
# 67 0xffbe (F1) 0xffc8 (F11)
# 68 0xffbf (F2) 0xffc9 (F12)
# 95 0xffc8 (F11)
# 96 0xffc9 (F12)
#
# The above output is one reason why FVWM might think that a binding
# to key 'F11' should become active when either a keycode 67 or a keycode
# 95 is received. The fact that (apparently) FVWM does not allow two
# events to be bound to one keycode allows us to fix the situation by
# placing the definitions for keys F11 and F12 before those of F1 and F2.
# Thus, when F1 is bound, it "steals" the keycode 67 association from
# F11, which previously was in possession of it.
Brendan
--
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 Sat Aug 25 2001 - 08:12:10 BST