[signorovitch]

My only issue with ghostty is it isn’t immediately recognized by some programs through ssh (eg less) and they don’t operate properly. However there’s a one liner that solves the problem permanently on the remote machine[0] so it isn’t too bad. Hopefully in the near future ghostty’s terminfo will be shipped with common linux distros.

[0] https://ghostty.org/docs/help/terminfo

[oofbey]

I find this docs page fairly hilarious. Complaining about how the rest of the world is in the stone ages, and that is why ghostty doesn’t work with it.

For me, a terminal program that requires me to muck with every machine I log into to get it to work is pretty horrible. I connect to a lot of different machines every work dat. Often they’re not machines I maintain. Making that harder is exactly the opposite of what I want from a key tool like a terminal program.

[cbushko]

All of those terminals work for you now because someone went and added terminfo to ncurses which distributed it across all versions of linux.

Kitty needed to do it too back in 2018.

https://lists.gnu.org/archive/html/bug-ncurses/2018-09/msg00...

Note: Ghostty follows the same pattern as Kitty where they a) use their own terminfo, b) distribute it when ssh'ing (it gets pushed to the remote server) and c) added it to ncurses so that it will eventually go away.

[randusername]

Apparently changing $TERM from `screen-256color` to `tmux-256color` in tmux to try and get italics working in nvim totally mangled ghostty.

I looked into infocmp and other tricks to try and and figure out why the backspace key was throwing gibberish around, but I had no interest in debugging such an inscrutable thing through so many layers.

I don't fault ghostty for things like this, but at the same time it's hard not to scorn the tools you want to be invisible, even if making unreasonable demands of them on accident.

[dmix]

I haven't used ghostty but terminal having issues with ssh sounds like a major oversight.