On Sun, Jun 05, 2011 at 07:27:51PM +0100, Thomas Adam wrote:
> On Sun, Jun 05, 2011 at 08:12:29PM +0200, Kalten wrote:
> > I want FireFox to ignore C-q.
> > I used
> > Key (Firefox) Q A C Exec exec xterm
>
> This will work just fine because you're not asking FVWM to then try and send
> the event to Firefox.
>
> > Key (*) Q A C --
> > Does not change the behaviour in the right way: If I use the sequence
> > Key (Firefox) Q A C Exec exec xterm
> > Key (*) Q A C --
> > Even FireFox does not react on C-q, and does not receive it at
> > all---just flicker like ``git gui'' (as described earlier here).
> > If I use the sequence
>
> That's a bug. I'll commit a fix to CVS for this in due course.
Or not. I mis-remembered here. So I looked at the code. Whenever one sets
a window-specific key-binding, FVWM then compares all the bindings it
receives, and always then sends the binding on, which can only be synthetic
at this point.
So even if you had this:
Key (Foo) Q A C Exec exec xteddy
Where previously ^Q on dear little xteddy did something, if he doesn't
respond to synthetic events, no amount of ^Qs will make him work until all
global window-bindings are cleared from FVWM.
There is nothing I can, or will do about this. The applications in question
must either learn to accept and understand synthetic key events (with an
appropriate option) or go back and see my previous solution, but this is
going to likely be tedious for you.
That's really my final word on this -- there's nothing more for me to do or
suggest to you.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
