-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bash: kitten: command not found #7160
Comments
works fine for me sshing into a bash system. You can always just |
@johnnypea I don't know if this helps but kitten might be there in kitty.app which is downloaded you can just do a symbolic link for me it was |
I went digging for the root cause of this, and it's because debian hard overwrites PATH in /etc/profile:
which is sourced by:
so we lose the added path component which is sent in the environment. It may make sense to add the ...kitty-ssh-kitten/bin path at the very end of the injection script, so any path manipulation in system/user rc files doesn't remove it. |
The injection scripts are meant for shell integration, not making kitten available in PATH. kitten needs to be available in PATH even when shell integration is disabled and thus no scripts are sourced. That is why it is injected via env var manipulation. Debian really shouldn't be overriding PATH especially for user shells, this can really only be fixed properly in Debian. I will note that no other major linux distro does this as far as I know. I checked Arch, Fedora and Ubuntu. Checked via podman run --interactive fedora sh -c "cat /etc/profile; PATH=/some/user/add /bin/bash -ilc 'echo \$PATH'" Outputs
as expected /some/user/add is present in PATH |
I guess waiting for Debian to fix this is pointless, so I will fix it at least for the case of the ssh kitten when shell integration is enabled. If the user disables shell integration then the fix wont work, but ... |
MacOS Sonoma 14.3.1
fish, version 3.7.0
kitty 0.32.2
Using
kitten ssh
but I'm not able to usekitten
command in "Debian GNU/Linux 12 (bookworm)" bash shell.Thanks.
The text was updated successfully, but these errors were encountered: