New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Escape key not detected the first time #21
Comments
I can confirm this is happening for me too with the |
i'll go ahead and make one, thanks! |
This is not happening for me in Kitty, fwiw. About to attempt verification with alacritty/XTerm. |
confirmed in alacritty/xterm. further work will take place in dankamongmen/notcurses#2646. Thanks for the report! |
i've fixed this upstream, to the best of my testing, and will cut 3.0.8 within the next few days including this fix. hack on everybody |
On fetching input, Escape key event doesn't seem to be detected the first time. It takes two key-presses to detect Escape key for the first time after which it is detected at each key press.
Reproducible example -
Viewing the logs
RUST_LOG=trace cargo run
would reveal that each other keyboard input (characters, Tab etc) is detected on one key-press, only Escape key takes two.The behavior is the same if I don't use polling and simply loop delayed
get()
. My Escape key appears to be registering perfectly for other applications so I doubt it is the issue.Terminals - Alacritty, XTerm.
Please confirm this if this behavior is reproducible and is a bug.
The text was updated successfully, but these errors were encountered: