zsh's bindkey not working for shift-enter

[rhuss]

I've used iTerm2 for too long, and I'm ready to switch to this great terminal emulator.

The last thing that bothers me is that I get the following bindkey command not working.

bindkey '^[SE' autosuggest-execute

which binds to SHIFT-ENTER in iTerm, but on Ghostly, I get a ;2;13~ output when pressing SHIFT-ENTER. Other bindings like bindkey '^[[Z' reverse-menu-complete work smoothly (this is on SHIFT-TAB)

I've searched the discussion history and the documentation but couldn't find an answer. What would be the best way to bind a zsh command to SHIFT-ENTER in Ghostty?

[00-kat]

It's not the same key combination, but it's the same underlying issue as #3151 (reply in thread). TL;DR: Ghostty implements fixterms, which many other terminal emulators don't; you can either change your bindkey or rebind shift+enter to send the same sequence as iTerm2.

[rhuss]

Thanks @00-kat for the pointer! While I'm definitely not deep into the matter, I found out that I hat an explicit key binding setup in iTerm to map Shift-Enter to esc-S-E which I send used in a bindkey in my zsh config. So the solution is quite simple for this use case:

keybind = shift+enter=esc:SE

in ghostty's config and to bind to the autosuggest-execute widget in I kept, in zsh config:

bindkey '^[SE' autosuggest-execute

In summary, I already used a 'hack' to map Shift-Enter in iTerm (i.e. mapping to a free escape sequence), I just have forgot 🤦 (but this info might be helpful for other use cases, too)

[00-kat]

Instead of doing the same binding in Ghostty's config, you might want to consider bindkey '^[[27;2;13~' autosuggest-execute instead (or perhaps add both ^[SE and ^[[27;2;13~ so that you can use the same config across multiple terminal emulators if you need to), since fixterms already maps shift+enter to a free escape sequence for you.

[rhuss]

Thanks, that also works like a charm (tbh, I was not able to find out what CSI looks like in zsh's bindkey syntax, highly appreciate your suggestion)