Repository navigation
Report terminal support for CSI-u #967
Description
It would be useful to know whether the terminal supports kitty's keyboard protocol. There is a way to detect this, described here. Applications can make use of more advanced keybindings if they know it's available.
Would you consider adding an API to Screen to query this? We are still on v2, and upgrading to v3 is quite a bit of work for us, so it would be awesome to have this available in v2; but I understand of course if you don't want to add things to v2 any more.
Activity
gdamore commentedon Jan 4, 2026
Indeed I'm not really trying to keep adding things to v2. After all I need some carrots so people upgrade -- and honestly its a lot more work to maintain multiple featureful branches.
Note that you probably also want to know about Win32 input mode, which has the same richness as kitty's protocol.
Which also begs a question about the Modify Other Keys protocol from XTerm. I suspect that's less interesting for you, even though it does avoid much of the ambiguity present in the legacy protocols. (You can for example discriminate between control I and control J.)
stefanhaller commentedon Jan 5, 2026
Yes, fully understood, and I expected this.
I wasn't aware that there are other protocols than the kitty one. Sure, if they are detectable, this would be great to know about too.
feat: Add reporting of keyboard protocol (fixes #967)
feat: Add reporting of keyboard protocol (fixes #967)
feat: Add reporting of keyboard protocol (fixes #967)