Closed blyzer closed 6 months ago
What do you mean by doesn't replace the cd
command?
I have the same problem. Adding zoxide init fish | source
to the end of fish config file works fine. However, zoxide init --cmd cd fish | source
doesn't add zoxide to fish.
However,
zoxide init --cmd cd fish | source
doesn't add zoxide to fish.
I've still not fully understood - what do you mean by "zoxide is not added to fish"? Also, what is your fish version / zoxide version?
I have zoxide init --cmd cd fish | source
in my fish config at ~/.config/fish/config.fish
when I launch a new terminal and run which cd
I get /usr/bin/cd
If I run zoxide init --cmd cd fish | source
in a terminal I get the same result.
Running alias
I do get the following results
alias cd __zoxide_z
alias cdi __zoxide_zi
And when I try to use zoxide as described it does work
For example cd code
will take me to ~/dev/code
from the home directory
On MacOS 14.2.1, Fish v3.7.0, zoxide 0.9.4
@andyw134 the which
command locates binaries with a given name, whereas zoxide defines cd
as a function. Is there any issue you're having with the setup?
No issues, but I initially thought it was not working. Was contributing my experience in case it would help others.
Thank you, I had the exact same setup and too thought that because which cd
returned /usr/bin/cd
it wouldn't work. I know now that it does. Thanks for sharing 👍
Cool cool, closing this issue.
using --cmd in fish config configuration doesn't replace the cd command
I have reopened three times.
here is my configuration: