On Sat, Apr 12, 2008 at 2:51 AM, Duncan Watts <
address@hidden> wrote:
Hi
When my laptop is running with a high load, keyboard input meant for
Stumpwm often goes through to the focussed application instead: For
example, I have the prefix mapped to the windows key and use the Fn
keys to switch groups and under load Stumpwm misses the prefix key and
the F1 goes through to firefox bringing up the help page.
With zero knowledge of programming window managers I would have
assumed that all keyboard input passed through stumpwm before being
directed to the appropriate application and would be queued up when
Stumpwm is busy, but this seems not to be the case. Would this be
considered a bug or just the expected behaviour based on the input
model implemented in Stumpwm?
It wasn't always like this. Stumpwm used to capture all input and deal with it properly except sometimes it would mysteriously hang. This had something to do with how stumpwm reserved the top level bindings. It told X to deliver the key event to stumpwm and also freeze the keyboard so no other events would be processed (events would still queue up on the server) until stumpwm thawed the keyboard. It was a great idea and should have worked, but caused too many hangs and I couldn't figure out why (it didnt help that my computer didnt hang except for rare exceptions).
So now stumpwm doesn't freeze the keyboard and computers don't hang. Unfortunately, now you have to be a bit more cautious when sending that second key press.
I would love it if an X guru teleported in and first explain what I was doing wrong and then supply a patch :).
-Shawn