On Sun, Jul 07, 2002 at 11:00:04PM +0200, Remko Troncon wrote:
> I have been coping with a specific problem ever since i started using
> fvwm one year ago. For some reason, from time to time my key bindings
> stopped working, and closing windows by clicking on the button in the
> top left corner of the window didn't work either.
Oh dear! You've lived with the most frequently encountered
problem for a year without knowing that the solution is written in
big friendly letters right at the front of the fvwm FAQ. ;-)
> Because i couldn't
> reproduce the error, i didn't mention it (yet). However, i seem to have
> found the reason: going into 'Scroll Lock' mode seems to change some
> things that make fvwm ignore these events. It's a mystery to me how i
> get into that 'scroll lock' mode, but pressing scroll lock seems to
> solve the problem every time (and pressing it again causes the events to
> be ignored again).
> Is there a solution to this ?
Yes. The one I recommend is to disable the scroll-lock, num-lock
and possibly caps-lock keys conpletely. From our FAQ (note that you
need at least fvwm-2.4.0 for the IgnoreModifiers command):
-------------------------- snip ----------------------------
5.5 Why do NumLock, CapsLock and ScrollLock interfere with
ClickToFocus and/or my mouse bindings?
A: Because they are treated as modifiers. You can use the
IgnoreModifiers command to turn individual modifiers off for
bindings. With XFree86 the right command is
IgnoreModifiers L25
If you changed your modifiers manually or are using a different
X server use the 'xmodmap' command to find out which modifiers
correspond to the keys you want to switch off.
This command creates a lot of extra network traffic, depending
on your CPU, network connection, the number of Key Mouse commands
in your configuration file and the number of modifiers you want to
ignore. If you do not have a lightning fast machine or very few
bindings you should not ignore more than two modifiers. So do
not ignore scroll-lock if you have no problem with it.
A better way to solve this problem is to modify the keyboard
mapping of your X server. The commands
xmodmap -e "clear Lock"
xmodmap -e "clear Mod2"
xmodmap -e "clear Mod5"
remove the CapsLock, NumLock and ScrollLock from the keyboard map.
Pressing these keys has no effect then. To re-add them try this:
xmodmap -e "add Lock = Caps_Lock"
xmodmap -e "add Mod2 = Num_Lock"
xmodmap -e "add Mod5 = Scroll_Lock"
Fvwm has to be restarted to use the changes made by xmodmap.
Please refer to the man page of the xmodmap command for further
details. If you disable the CapsLock key in your keyboard map in
this way, you can speed up fvwm a bit by removing the Lock
modifier from the list of ignored modifiers:
IgnoreModifiers
-------------------------- snip ----------------------------
Don't hesitate to ask for further help.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, dominik.vogt_at_gmx.de
Reply-To: dominik.vogt_at_gmx.de
--
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 Sun Jul 07 2002 - 18:45:58 BST