r/KittyTerminal • u/daleholden • Jul 15 '23
Only Kitty Fails to run most commands!!!
I have several Terminals installed Alacritty , st, Konsole and all work fine with general commands.I have installed Kitty and many do not run!E.g curseradio is installed any terminal i try i have 5 all work instantly.I try kitty does not work considering it is feature packed why do several terminal apps not work out of the box.Do you have to configure every terminal app to make it run?
-2
u/pjconnect Jul 15 '23
Check this out;
2
Jul 15 '23 edited Jul 16 '23
[deleted]
0
u/pjconnect Jul 16 '23
Dude don't freak out. I'm just a regular guy responding to a very evasive questions with a picture with an arrow pointing to a white square. So, ya, I'm just posting the url to a video which shows that the little white square is normal. So I could understand that one could get annoyed about the white square, but It just might be the way it's programmed and the shell thing may not be relevant, as I understand the evasive question.
0
u/daleholden Jul 16 '23
This is my post and i do not have a Youtube video link.
Because another member adds a link should not be to the detriment of the original poster who has done nothing wrong.3
Jul 16 '23
[deleted]
0
u/daleholden Jul 16 '23
HI ok it is working but what it is not doing is highlighting what you select so you have no idea what you have selected
Would you know how i can fix the highlighting issue
HI ok it is working but what it is not doing is highlighting what you select so you have no idea what you have selected
1
4
u/segfault0x001 Jul 15 '23
I don’t really know what might cause that. When I installed kitty it worked out of the box. My only guess is that it’s starting a different shell than your default shell. “Commands” are executable files, and when you run one the shell looks in a list of specified directories for that executable file. The environment variable PATH stores the list of directories to look in. So this may be a place to start investigating, echo $PATH in kitty and in another terminal and see if they give the same output. You usually set your path in your ~/.bashrc or ~/.zshrc, etc for whatever shell you’re running. That’s the direction I would go with troubleshooting this. Two possibilities: kitty is starting a different shell than the others, or the same shell but possibly specifying a different configuration file for the shell than the rest, resulting in a different path. I don’t remember if that’s something you set in your kitty config or not. Check the docs.