FVWM: pass on all keyboard events to client window

[g***@yahoo.de]

Hi,

I defined lots of keyboard shortcuts for fvwm. With most programs that
I use, I manage to either change the keyboard bindings for fvwm or for
the program in question to avoid collisions. Unfortunately there are
rare occasions, where this is not possible.

Is there any way to tell fvwm to pass all keyboard events to a specific
client window if it has the focus without making this window completely
unmanaged?

Regards,
Peter

[Dominique Michel]

Le Fri, 31 Jan 2014 12:54:31 +0100,

Post by g***@yahoo.de
Hi,
I defined lots of keyboard shortcuts for fvwm. With most programs that
I use, I manage to either change the keyboard bindings for fvwm or for
the program in question to avoid colilisions. Unfortunately there
are rare occasions, where this is not possible.
Is there any way to tell fvwm to pass all keyboard events to a
specific client window if it has the focus without making this window
completely unmanaged?

No, fvwm key bindings are global. What you can do is to change the
keyboard modifiers. As example you can use 4 instead of M, and 4S
instead of MS (4 is the Windows left key or Super_L).

Key F A 4S SomeFunction

Best,
Dominique

Post by g***@yahoo.de
Regards,
Peter

[Thomas Adam]

Post by Dominique Michel
Le Fri, 31 Jan 2014 12:54:31 +0100,

Post by g***@yahoo.de
Hi,
I defined lots of keyboard shortcuts for fvwm. With most programs that
I use, I manage to either change the keyboard bindings for fvwm or for
the program in question to avoid colilisions. Unfortunately there
are rare occasions, where this is not possible.
Is there any way to tell fvwm to pass all keyboard events to a
specific client window if it has the focus without making this window
completely unmanaged?

No, fvwm key bindings are global. What you can do is to change the
keyboard modifiers. As example you can use 4 instead of M, and 4S
instead of MS (4 is the Windows left key or Super_L).

Application-specific bindings would be the way to go here---but
they're broken in FVWM. You could still try though (assuming the
application responds to synthetic events), hence:

Key (SomeWindow) Foo Bar --

Note the "--" which indicates it should pass on the key event to the
application.

-- Thomas Adam