Skip to content
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

Don't use kitty sequences outside protocol #7677

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

kchibisov
Copy link
Member

Originally kitty defined that functional keys, which are not encoded by default, like Pause should be encoded with CSI u. However the specification was clarified and now it says that terminal may ignore that part. Given that Alacritty tries to follow xterm/urxvt when it comes to bindings, CSI u bindings are not send for consistency reasons.

This also brings back F13-F20 bindings used by Alacritty in 0.12.3, as well as explicitly defines NumpadEnter like it was before.

Closes #7623.

Originally kitty defined that functional keys, which are not encoded
by default, like `Pause` should be encoded with `CSI u`. However
the specification was clarified and now it says that terminal
may ignore that part. Given that Alacritty tries to follow xterm/urxvt
when it comes to bindings, CSI u bindings are not send for consistency
reasons.

This also brings back F13-F20 bindings used by Alacritty in 0.12.3, as
well as explicitly defines `NumpadEnter` like it was before.

Closes alacritty#7623.
@kchibisov kchibisov merged commit 38d63ab into alacritty:master Jan 30, 2024
5 checks passed
@kchibisov kchibisov deleted the kitty-no-default branch January 30, 2024 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants