Closed imwints closed 2 weeks ago
I'm afraid that's not a scenario I am interested in trying to support. Running exec replaces the process at which point there is nothing the kitten can do anymore since it has been replaced. You can try using python as the kitten interpreter, that might workaround it.
Thanks for the quick reply. I have troubles understanding why this occurs in the first place and how I might force python as the kitten interpreter :)
The documentation of the kitten tells you how to set its options and as to why it happens, its because on the remote side something ran your shell instead of the kittens remote script, which reads all that data. So that data was left pending and ended up on your screen.
And incidentally if you want to run some non login shell on the server like fish the correct way to do it is to set the login_shell option for the ssh kitten, then it will do it for you.
Similar to https://github.com/kovidgoyal/kitty/issues/6254 I have a dump of KITTY_DATA_START in the terminal after a second login in a session. This started to occur when I set my shell on the remote system to start
fish
in the~/.bashrc
, it looks the following:To Reproduce
kitty +kitten ssh <remote>
kitty +kitten ssh <remote>
Environment details
Additional context I have the same bash to fish setup on my local machine.
I launched kitty from the terminal like
kitty --config NONE
and can reproduce the issue, however the following pops up a couple hundred times on the first console, maybe it's interesting: