https://vninja.net/tags/terminfo/Recent content in terminfo on vNinja.net | VMware, VCF & HomelabHugo -- gohugo.ioen&copy; 2010 - 2026 <b>vNinja.net</b> <br/> <em>There is a thin line between agile and fragile</em>Mon, 20 Jul 2026 13:38:07 +0200https://vninja.net/2026/07/19/ghostty-ssh-terminfo-whats-actually-fixed/Sun, 19 Jul 2026 00:00:00 +0000https://vninja.net/2026/07/19/ghostty-ssh-terminfo-whats-actually-fixed/Ghostty shipped a partial fix for its SSH terminfo problem back in version 1.2.0, and a proper one is coming in 1.4.0. I went looking for why I was still running into trouble, and found the real story is more complicated than either release note lets on.https://vninja.net/2024/12/28/ghostty-workaround-for-missing-or-unsuitable-terminal-xterm-ghostty/Sat, 28 Dec 2024 00:00:00 +0000https://vninja.net/2024/12/28/ghostty-workaround-for-missing-or-unsuitable-terminal-xterm-ghostty/The freshly made public Ghostty terminal emulator by Mitchell Hashimoto (co-founder of Hashicorp) is all the rage at the moment, and it definitely looks interesting! <br/><br/> The first real issue I had with it, was when using SSH to connect to remote resources. This produced the `missing or unsuitable terminal: xterm-ghostty` error message, because the remote resource doesn't have the `xterm-ghostty` terminfo defined. The official Ghostty docs has some workarounds for it, but these are either to convoluted like copying terminfo entries to all remote systems, or setting `SetEnv TERM=xterm-256color` in `.ssh/config` for each remote host. The other alternative is to set `SetEnv TERM=xterm-256color` system wide but that also affects other terminal emulators (as does setting it in `.ssh/config`)