-
Notifications
You must be signed in to change notification settings - Fork 516
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
Partial match high priority nested path over exact direct descendent (edge-case) #825
Comments
The only way to solve this particular case is to use a query that will not match a local directory. Here's some alternatives:
|
Thanks for your response. I am aware of the workarounds, but the example I gave is one of many. The issue - for me at least - is that although
What I'm suggesting is to make that semantically clear, or to provide that as an option. It makes more sense to me at least. Operands resulting in a physical pathspec behave like |
It's easy enough to implement - zoxide is designed with scriptability in mind. What you're asking for can be achieved with a simple one line function:
|
Wasn't aware of that - thanks. However, that's not quite what I'm looking for. The above only works with parameters that match entries in the db, and doesn't work in situations where I want to do a straight
Sorry to trouble you further, but is it straightforward to achieve that? So if I'm in Appreciate for your help 🙂 |
As far as Linux is concerned, You could certainly write a custom script that only tries to manually |
In
~
I have 2 folders:The latter is in z's db with a high priority (80+).
z go
from anywhere I end up in~/dev/srv/api-go
(wanted behaviour)z go
from~
it takes me to~/go
(unwanted behaviour)Can this be fixed without excluding
~/go
entirely? So I could still typez ./go
orz ~/go
to get there, but in all other casesz go
matches~/dev/srv/api-go
.I'll admit this is an edge case but it's been chafing with me lately. Perhaps a negative score in
zoxide edit
would indicate such directories?Apologies in advance if I've missed anything obvious 😉
The text was updated successfully, but these errors were encountered: