You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using --cmd cd to make zoxide take over my cd.
It would be helpful when navigating around to more easily tell when zoxide jumped to a directory rather than just having passed a valid path to cd into.
E.g. if I cd foo, if there actually is a foo directory, then don't echo. If there isn't but one was found in the database, then do echo. By only printing in the latter case, it makes it easier to tell when zoxide logic kicked in and whether that matched my expectation. For example, if I typo'ed a local directory, I would be surprised to see the echo and realized what had happened more easily.
The text was updated successfully, but these errors were encountered:
zoxide is designed to be hackable. It's fairly easy to build something like this by replacing the underlying command - you inspect the result of zoxide init <your shell>, and change it to whatever you like.
I'm using
--cmd cd
to make zoxide take over mycd
.It would be helpful when navigating around to more easily tell when zoxide jumped to a directory rather than just having passed a valid path to
cd
into.E.g. if I
cd foo
, if there actually is afoo
directory, then don't echo. If there isn't but one was found in the database, then do echo. By only printing in the latter case, it makes it easier to tell when zoxide logic kicked in and whether that matched my expectation. For example, if I typo'ed a local directory, I would be surprised to see the echo and realized what had happened more easily.The text was updated successfully, but these errors were encountered: