zlacker

I really love Ghostty. Thanks to it, my comeback to (n)vim has been quite smooth. Keybindings with the CMD key works right away without having to send any escape sequence or similar. It just works™

>>dagi3d+(OP)
ive found ghostty to be a pretty decent replacement for iterm2, some bugs still being worked out and i havent always had the best luck with the guake dropdown style terminal but all in all it's pretty nice. sort of miss the additional hot-key invoking options iterm2 had (i could double tap control or cmd to invoke) and ghostty is a lil more limited there, but overall its solid, doesn't feel bloated. iterm2's settings gui was a total tragedy. there was some xterm related issue i ran into ssh'ing into a vps but i can't even remember for the life of me what that was.

i didnt even consider that having to configure everything with a config file allows apps like this https://github.com/zerebos/ghostty-config to exist. neat

>>trueno+l1
i agree, you can search in the terminal like you can iterm2 either, which is super annoying.

>>misiti+H7
It’s merged to main but not in any district channels yet AFAIK

>>trueno+l1
Regarding the SSH issue (if anyone else reading this had the same):

Certain CLI tools complain about unknown $TERM env vars. For example, I could not open vim when SSHing into my Hetzner VPS in Ghostty. The fix is to set TERM to some well-known alternative before running your tool, like so: TERM=xterm vim

>>pprota+Os1
oh my god this was it. thank you!! (i never fixed it but im going to now!)

>>pprota+Os1
adding this should also do the trick: shell-integration-features = ssh-env