CSI u enable/disable through escape sequence
Kitty recently implemented a new extended keyboard protocol based of the
CSI u proposal that iterm2 already supports. One extension of interest is the ability for applications to enable/disable it themselves when iterm2 currently only supports this through the profile configuration.
This is an issue because applications such as the shell that do not handle
CSI u get confused when it is enabled in the profile. For example pressing shift+space in bash (quite common for me after typing
| because I dont release the shift key quickly enough) ends up inserting
;2u in the prompt.
It would be nice if iterm2 supported at least the basic
CSI > 1 u for enabling the existing support and
CSI < u to disable it.