[QUESTION] does kakoune support modifyOtherKeys level 2?

[terminalzeiro]

Question

I trying to bind <c-s-w>, but kak reconize that as <c-w>.

• terminal that I'm using: xterm 379
• modifyOtherKeys=2
• formatOtherKeys=1 ("CSI u" for extended keys)

[krobelus]

On Sun, Jan 12, 2025 at 04:45:10PM -0800, terminalzeiro wrote: does kakoune support modifyOtherKeys level 2? I trying to bind <c-s-w>, but kak reconize that as <c-w>. terminal that I'm using: xterm

Not yet. It should be doable to add. I think we could change \033[>4;1m to \033[>4;2m and maybe add some key decoding logic to src/terminal_ui.cc. Unfortunately xterm doesn't send CSI u by default (see formatOtherKeys) but the default format might still be good enough. I wonder what should be the long-term plan. We're mixing modifyOtherKeys with the kitty keyboard protocol, which is both good and bad.

[Screwtapello]

Unfortunately xterm doesn't send CSI u by default (see formatOtherKeys)
but the default format might still be good enough.

It doesn't, but it's easy enough to change if a lot of apps use the Kitty protocol, and Kakoune learn to parse the xterm syntax in commit 2c923ba.

[terminalzeiro]

interesting info: tmux since 3.5 works with modifyOtherKeys level 2 and "CSI u" (new server option extended-keys-format).