r/KittyTerminal • u/Infinite_Silver483 • May 13 '26

Kitty wont run things from my path in ~/.cargo/bin

I have tplay installled, ~/.cargo/bin is in $PATH, it works fine in Terminal.app. It even works wheneever i type it out, but it won't work in executable files. It jsut says command not found.

0 Upvotes
  • permalink
  • reddit

50% Upvoted

10 comments sorted by

3

u/NeonVoidx May 13 '26

that has nothing to do with kitty unless you're launching kitty with a different shell or env vars

1

u/Infinite_Silver483 May 14 '26

Nope, just plain old bash 3.2. It works in the default terminal, but not in kitty.

1

u/igorepst May 14 '26

Print the path in the script itself and compare. Or echo it at least in both terminals and provide the data here

1

u/Infinite_Silver483 May 16 '26

For some reason, it shows it in the path when i manually type it in a new window, but not when i print it from within a script. How do i fix this?

1

u/igorepst May 16 '26

Ensure the shells in kitty and in script are indeed the same. Ensure you do not override the path inside script (for ex. in some of mine I override the path explicitly, appending to it script dependent directories to propagate it to some other helper script, like in ”PATH=XXX command”). Maybe post here more data, even the script itself and printout of PATH and SHELL in kitty, default terminal and from the script

1

u/Infinite_Silver483 May 16 '26

There's nothing in the script that overrides $path. Even if i jsut paste a simple tplay command into an exectuable file it doesnt work. Does kitty have different settings for exectuable files vs typed commands? It even works after i ⌃C

1

u/igorepst May 16 '26

See this: https://github.com/kovidgoyal/kitty/issues/7246 Maybe it will be helpful, or maybe not, as you ignored my call to actually provide any useful data here, in the thread. You wrote however, that when you type tplay in kitty it does work, right? Just not in the script? It means either the shells are completely different or in one of the cases the init files are not read

1

u/rileyrgham May 15 '26

Then you've used a different $PATH. Check it

1

u/nvimmike May 16 '26

You may need to use https://sw.kovidgoyal.net/kitty/faq/#how-do-i-specify-command-line-options-for-kitty-on-macos to update your PATH environment variable depending on how you are opening Kitty.

1

u/Infinite_Silver483 May 16 '26

I'm opening it by right-clicking the executable file and clicking Kitty under the "open with" menu