David Keijser

There is some odd parts of bind.py where we do a round trip to core and back that is likely causing this. Because a second key press event might occur...

ok. if typing speed matters it pretty much has to be this round trip. I'm guessing the issue with ddg only happens shortly after switching mode into the prompt?

I don't think there is any reason it _has_ to make a round trip so the latency shouldn't really matter. However dispatching quick events in core with javascript could help...

I tried adding some tests to the event manager to trigger this but couldn't get it to reproduce. I also tried piping a event stream into uzbl also not triggering...

hmm. It's very tricky when I can't see it for myself. Maybe you could try capturing a log of events from when this is happening (using the -p) flag. Maybe...

This line after "key press e" is very suspicious ``` EVENT [2456] VARIABLE_SET keycmd str '' ``` So what happens here is the keycmd is reset so the next key...

could you try removing ``` @on_event ROOT_ACTIVE event KEYCMD_CLEAR @on_event FOCUS_ELEMENT event KEYCMD_CLEAR ``` and anything else that migth be running KEYCMD_CLEAR from the config. maybe also any automatic mode...

hmm ok. that's really weird. the ESCAPE event should only happen from pressing Escape (or "Ctrl+[") so unless you are doing that mid sequence I don't see how that should...

oh but wait. in the logs you are pressing escape right before entering triggering the follow script. and because that does a round trip with the `event ESCAPE -> event...

So I guess what we need to really solve this as a mechanism (and a syntax) for dispatching events from keybinds and on_event rules without the roundtrip. Meaning the event-manager...