News for hackers. Stuff that matters.
Re:Kitty 0.50 by xnickb on Wednesday November 04, 2026 @04:57AM (#50363355)
I've had so many issues with SSH that I ended up ghosttying kitty.
Re:Kitty 0.50 by cybrox on Wednesday November 04, 2026 @07:10AM (#50364498)
Fixed with a single alias or a single ssh config entry.
Re:Kitty 0.50 by Geezus_42 on Wednesday November 04, 2026 @07:26AM (#50364634)
Ghostty made that obvious in the documentation for me. I haven't looked at the kitty docs, so Idk if they do as well.
Re:Kitty 0.50 by xnickb on Wednesday November 04, 2026 @08:05AM (#50365005)
If you mean the `alias ssh="kitty +kitten ssh"` then no, it's not fixed at all.

For example pikvm exists with read-only mounted filesystem. Having to dive into the details to figure out that the issue is kitty trying to write a file to make some obscure terminal features work doesn't strike me as good design.

`alias ssh="TERM=xterm-256color ssh"` fixes it but isn't mentioned in the docs.

Re:Kitty 0.50 by KetoManx64 on Friday November 06, 2026 @11:43AM (#50394751)
> TERM=xterm-256color ssh

Yep, i switched to kitty a few months ago and Claude dug around and found the solution external to the docs. The developer is very opinionated about how he thinks you should use Kitty.

Re:Kitty 0.50 by wzdd on Wednesday November 04, 2026 @08:26AM (#50365239)
It’s actually fixed, for everything, with a single kitty config line which tells it to use xterm-256color as the terminal type.

I respect the man’s ideological correctness, but it’s not 1982 anymore and nobody is going to add more terminal types.