zoxide: detected a possible configuration issue.

[FuwaFuwa4242]

zoxide: detected a possible configuration issue.
Please ensure that zoxide is initialized right at the end of your shell configuration file (usually ~/.bashrc).

If the issue persists, consider filing an issue at:
https://github.com/ajeetdsouza/zoxide/issues

Disable this message by setting _ZO_DOCTOR=0.

whenever i execute the command z i get this error message but i have intialized it in my .bashrc since the last line is eval "$(zoxide init bash)"

[FuwaFuwa4242]

fixed

[clydeugene]

fixed

Hey @FuwaFuwa4242 if you don't mind, please may you share how you fixed it? I am assuming you did so without setting _ZO_DOCTOR=0 correct?

[ajeetdsouza]

@clydeugene did you follow the instructions printed on your terminal?

Please ensure that zoxide is initialized right at the end of your shell configuration file.

[FuwaFuwa4242]

i just swapped from bash to zsh and the bug was fixed, even if i had bash as my default shell it gave me the config error but after swapping to zsh it seemed to be fixed now it remembers my directories properly and functions as expected

[clydeugene]

@clydeugene did you follow the instructions printed on your terminal?

Yes I did. I am using bash and every time I start a new shell instance I get that message. For what it's worth, I installed zoxide as a local user, as I do not have sudo access on the Ubuntu server that I use.

i just swapped from bash to zsh and the bug was fixed, even if i had bash as my default shell it gave me the config error but after swapping to zsh it seemed to be fixed now it remembers my directories properly and functions as expected

That's interesting. Unfortunately I am stuck with bash as that is what works best for the lab that I am in.

[ajeetdsouza]

@clydeugene usually, this issue occurs because something is being initialized after zoxide, and is overriding it. For a lot of users, this happens due to Starship. If zoxide is at the bottom of your config, that shouldn't be happening - could you share your config here?

[clydeugene]

config_copy.txt

[ValentinGurkov]

My configuration also has zoxide last on Windows Git Bash and I get the same error.

eval "$(fzf --bash)"
eval "$(starship init bash)"
eval "$(fnm env --use-on-cd)"
eval "$(zoxide init bash --cmd cd)"

[ajeetdsouza]

@clydeugene @ValentinGurkov could you also paste the output of echo $PROMPT_COMMAND here?

[ValentinGurkov]

@clydeugene @ValentinGurkov could you also paste the output of echo $PROMPT_COMMAND here?

This helped, I think I know a bit more about this:

 echo $PROMPT_COMMAND
__vsc_prompt_cmd_original

It seems like VSCode injects its' own things. Disabling the shell integration will result in using the zoxide prompt:

"terminal.integrated.shellIntegration.enabled": false

echo $PROMPT_COMMAND
__zoxide_hook;starship_precmd

I am not sure if there are any other alternatives?