Closed grimm26 closed 1 year ago
Add /home/mkeisler/.local/kitty.app/bin/ to PATH and it will work, I will have shell integration do that automatically in the next release.
Actually, it should be in PATH already. You are presumably overwriting PATH in some shell rc script. If you do that then you need to add the PATH manually.
Before, kitty had only one executable, however, now there are two (kitty
, kitten
).
If your PATH does not contain the kitty bin folder, but uses symbolic links, then you need to create one for kitten
as well.
ln -sf $HOME/.local/kitty.app/bin/kitty ~/.local/bin/kitty
ln -sf $HOME/.local/kitty.app/bin/kitten ~/.local/bin/kitten
@kovidgoyal I think the documentation needs to be updated. Now it's two.
https://sw.kovidgoyal.net/kitty/binary/
Do not copy the kitty binary ... create a symlink in ...
PATH
.~/.local/bin
,/usr/local/bin/
...@page-down done
I'm not overwriting PATH, but I am using a symlinked kitty instead of having ~/.local/kitty.app/bin
in my PATH.
Ah yes, the you have to symlink kitten as well.
@page-down could you please implement https://github.com/kovidgoyal/kitty/commit/47641456dad9fee3e228dfa8361fdc88db317861 for the fish shell, I am not sure of the best way to do so there.
I went ahead and just added the kitty bin directory to my path instead.
Yeah either will work and with my last commit, edit-in-kitty will use the full path to kitten anyway.
Describe the bug The edit-in-kitty command fails.
To Reproduce Steps to reproduce the behavior:
Screenshots
Environment details