"zoxide: command not found" error on bash shell instance initialization, despite zoxide being accessible in $PATH

[dashelm]

Hello!
Just installed zoxide (Ubuntu Server 20.04.6 LTS), and I am having some trouble getting bash to play nice with it.

Namely, the eval statement provided in the documentation to be placed at the end of ~/.bashrc is causing "zoxide: command not found" to be printed whenever a new shell instance is created. The process is clearly not being started.

Entering "which zoxide" returns:
/home/dashel/.local/bin/zoxide

and echo $PATH returns:
/home/dashel/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/snap/bin:/home/dashel/.dotnet/tools

I'm able to use the "zoxide" command, proving that zoxide definitely exists somewhere, but the "z" command does not work.

zoxide's install location is included in $PATH, so why might bash be unable to find zoxide? And why might the "z" command be broken?
Thanks!

[AbdifitahW]

I'm facing this same issue and only once sourcing my .bashrc file does the z command function again.

[ajeetdsouza]

Somehow, it seems like ~/.local/bin is being added to your $PATH after you call eval.

Try adding export PATH="$HOME/.local/bin:$PATH" just before you calleval in your .bashrc.

[dashelm]

This worked!
Thank you so much for the help.

[abhishekchoure]

This worked for me as well. (Ubuntu WSL)

[jkottler]

In a similar situation, using Ubuntu 22.04 on WSL2, I found that the answer was to put the eval line at the end of ~/.profile instead of ~/.bashrc.