-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
take advantage of kitty keyboard protocol #2131
Comments
looks like the kitty keyboard protocol disables the standard line discipline:
|
i've started the |
looks like we also need to make the switch to the alternate screen (if we intend to do it) before sending any of this, as the keyboard context is per-screen. added another item. |
looks like there's some limited support for this using |
yeah we definitely need to move our push and set after |
shit, this means we can't do |
we need to leave the alternate screen in most |
alright, i've completed the handling of level 1, except we need to turn ctrl+{c, q, } into SIGINT and friends. |
hrmmm, arrow keys are having unexpected results. |
I think we're good to go for a merge here. I think there's a few more definitions I've not yet added, which we'll want to. Synthesis of signals is critical, but can't really be done properly until #2136 is complete, which I don't intend to do in 2.4.0. |
I thought i had a bug on this, but i guess not? https://sw.kovidgoyal.net/kitty/keyboard-protocol/ seems a reasonable thing to support. it would have a few parts:
CSI ? u
CSI ? flags u
CSI = flags ; 1 u
CSI > u
CSI < u
so throw the query into our initial query string. initialize
keyflags
to 0. if we get aCSI ? flags u
response, writeflags
tokeyflags
, and emit stepupCSI = flags ; 1 u
and pushCSI > u
.decode the inputs regardless of what flags said.
at exit, if we pushed, pop with
CSI < u
.The text was updated successfully, but these errors were encountered: