kitten ssh doesn't work with fish shell #3405
Describe the bug
The text was updated successfully, but these errors were encountered:
Oh and PRs to improve the wording in the FAQ are most welcome, https://sw.kovidgoyal.net/kitty/faq.html#i-get-errors-about-the-terminal-being-unknown-or-opening-the-terminal-failing-when-sshing-into-a-different-computer
relevant file is docs/faq.rst
It seems I need to do this to every server? I have a fleet of many hundreds of machines, and I don't want to force this step on to them. I'm not sure I understand why this is needed, I'll read the FAQ some more.
many terminal programs require the terminfo database of the terminal you are using to function. Those terminfo files need to get on your servers somehow. Servers come with pre-installed terminfo files for older terminals. Newer ones need their terminfo installed separately. You can use the ssh kitten aliased as ssh to avoid having to do this manually, unless it doesnt work because you have set your shell on the servers to be a non-POSIX compliant shell like fish. In that case use the python variant assuming you have python on your servers (the python variant is currntly not in released kitty version so you have to run kitty form master).
I tried the python variant but that gave me an error as well so I manually copied over the terminfo files which worked. However I was digging through the source and I observed that the script gets the shell dynamically. If kitty doesn't support fish, is it possible to simply execute the bash script with /bin/sh instead of fish so it won't complain about the syntax error.
has something like
edit: nvm I tried to compile from source with that change and it didn't work
the error is about