Re: [STUMP] key press detection lag?

[Ruthard Baudach]

>== Auszüge aus der Nachricht von  Eric Abrahamsen vom 2014-02-10 08:09:
> This could totally be my imagination, but since there have been so many
> updates recently, I thought I'd check in and see what other people
> think...
> 
> I'm running stump on archlinux, with no desktop manager. My subjective
> feeling is that I'm getting a lot of tardy prefix keypress detection
> from stumpwm: I hit "C-t c", which should run-or-raise my terminal, and
> instead a "c" gets sent to the focused window, and then stump picks up the
> "C-t" and waits for further input. This can be pretty annoying, for
> instance when emacs/gnus is focused and the unintentional "c" marks the
> group under point as completely read.
>
> Has this gotten worse recently, or am I dreaming? If I am dreaming, is
> there any way to block key input so that, even if stump is slow, it
> still consumes further keypresses?

I do not have this issue, but had it using C-t as prefix key -- it's too
uncomfortable for me to use it all the time.

I'm using the Windows key as prefix key:

.stumpwmrc:
---------------------->%-------------------
(run-shell-command "xmodmap -e \"keycode 133 = F20\"")
(run-shell-command "xmodmap -e \"clear Mod4\"")
(set-prefix-key (kbd "F20"))
---------------------->%-------------------

Of course, xmodmap has to be installed, and the Win key you are using
has to has keycode 133.

Use xev to check the keycode if necessary.

Greetings,
Ruthard