-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Feature Request: Go to next best match? #208
Comments
yeah i'm not interested in implementing something like this. it makes you think too much imo. knowing that the match i want is the second one is too much brain, and then what if it becomes the 3rd. z works best with the idea that one tends tp distinguish similar but different file paths in the mind already with a bit of shorthand ... if you use ~/Documents/foo, ~/Desktop/foo, ~/Pictures/foo all of the time, you're maybe already thinking along the same lines it was a very conscious decision not to have results in a list, that you could pick from. |
I agree with what you said, but my use case is different. If I use all of ~/Documents/foo, ~/Desktop/foo, ~/Pictures/foo very frequently, then it's useful to to think like But what happened with me was I had recently created all of ~/Documents/foo, ~/Desktop/foo, ~/Pictures/foo but I am only concerned with ~/Desktop/foo from now on and not the others So when I did So I wanted to do something like But I think I am not using this correctly. Would you say that in this situation I should first |
@peey, this is when the |
That's a good solution. Thanks @ericbn |
Let's say
z foo
lands you in a directorya-foo
but you wanted to go tob-foo
, would it be useful to implement a featurez -n
which could mean "go to the next best match"?And then whenever
z -n
is used, it could also "teach"z
to swap the rankings of the previous match with this match.Would it be useful to have or am I using
z
wrong?The text was updated successfully, but these errors were encountered: