-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zoxide: no match found on startup #782
Comments
Can you elaborate? |
P.S. you need cd to a directory the usual way at least once, so that zoxide can learn which directories you use. This video might help: https://www.youtube.com/watch?v=aghxkpyRVDY |
I am so sorry for the late reply.. I did use cd at least once, my understanding is that using but if I use this setup i can no longer use cd nor z? |
Something is definitely wrong with your bashrc configuration. If you can share it here, I can take a look. |
Thank you so much QAQ I believe the ~/.bash_aliases file is empty so that shouldn't be the problem |
zoxide -V
|
You have 2 versions of zoxide installed on your system. I'm guessing you first installed it using To fix this: sudo apt remove zoxide In your .bashrc: export PATH="$HOME/.local/bin:$PATH"
eval "$(zoxide init bash --cmd cd)" |
That solved the issue. My god you are a genius! |
I'm having a similar issue and I've tried everything mentioned in this issue so far. I used the script to install zoxide and added it to my .bashrc. When I Bashrc$HOME/.local/bin is already in $PATH OS: Ubuntu 22.04.4 |
I'm using a wsl ubuntu on a windows machine. when i first start up my wsl, the cd command doesn't seem to work?
In my .bashrc:
Weirdly it works after i either source the bashrc again, when i run
eval "$(zoxide init bash --cmd cd)"
manually, or when i remove the--cmd cd
. Why is this the case?The text was updated successfully, but these errors were encountered: