zlacker

[parent] [thread] 5 comments
1. trueno+(OP)[view] [source] 2025-12-03 19:58:03
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

replies(2): >>misiti+m6 >>pprota+tr1
2. misiti+m6[view] [source] 2025-12-03 20:25:00
>>trueno+(OP)
i agree, you can search in the terminal like you can iterm2 either, which is super annoying.
replies(1): >>jtbake+U41
◧◩
3. jtbake+U41[view] [source] [discussion] 2025-12-04 03:11:21
>>misiti+m6
It’s merged to main but not in any district channels yet AFAIK
4. pprota+tr1[view] [source] 2025-12-04 07:29:56
>>trueno+(OP)
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

replies(2): >>trueno+iL1 >>dagi3d+L02
◧◩
5. trueno+iL1[view] [source] [discussion] 2025-12-04 10:31:42
>>pprota+tr1
oh my god this was it. thank you!! (i never fixed it but im going to now!)
◧◩
6. dagi3d+L02[view] [source] [discussion] 2025-12-04 12:35:47
>>pprota+tr1
adding this should also do the trick: shell-integration-features = ssh-env
[go to top]