-
-
Notifications
You must be signed in to change notification settings - Fork 979
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
Wrong ESC-sequences for F-keys F1-F4 #3586
Comments
I cannot replicate this with kitty 0.20.3, running: kitty --config=NONE kitty +kitten show_key -m application and pressing F1 correctly displays ^[OP as expected. |
Oh and just for completeness, same without using the showkey kitten
also prints ^[OP as expected for F1 |
Hmm.. -- seems like you're right (and probably there are some issues in "micro" then).. also, to have "third party" test check, I've also tried "vi", and it was printing when F2, F3, F4 are pressed, so I'll open a bug report for "micro", let's see.. thank you for prompt support ! Rgds, -Dimitri |
If you don't set the terminal in Application Cursor Keys mode (don't print @kovidgoyal: Why does Application Cursor Keys mode change the function keys, not just the arrow keys in kitty? E.g. xterm sends |
Ah, that is indeed a regression, although note that cursor key mode |
Right, "just the arrow keys" wasn't completely accurate. |
Describe the bug
Both
xtrerm-ketty
andxterm-256color
terminfo are having F1-F4 keys as :while kitty is returning on these keys pressing the following :
e.g. there was somewhere missed "O" in output sequences..
and, curiously, this is happening only with F1-F4 keys, any other F-keys are working just fine.
To Reproduce
you can observe the problem with any Terminal app which is able to report pressed keys, and for me the most simple is to use "micro" for this :
raw
in command lineExpected behavior
the expected behavior is to see the sequences matching terminfo.
Environment details
OS: OSX Catalina (but I don't think OS plays any role here)
The text was updated successfully, but these errors were encountered: