On Friday, 2003.05.30, 09:44:36 +0200, Dominik Vogt wrote:
> To solve the problem, you should hard code the Xmodmap. You can
> generate a dump of the key map with xmodmap and put it in your
> $HOME/.Xmodmap:
>
> $ xmodmap -pke > $HOME/.Xmodmap
>
> You can then remove the xmodmap call from your start function.
This must be some kind of timing issue. I generated the dump like you
said, but fvwm still behaved the same way.
Running xev (without running my original xmodmap script), I found out
that X thinks Key 115 is the Meta_L key. I changed the Key command in
my .fvwm2rc file accordingly and now it works fine. Thanks for your
help.
--
Norvell Spearman
--
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 Fri May 30 2003 - 09:09:32 BST