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
And if I do z git it will go to the shellcheck directory. Since git has an EXACT match, I'd kind of prefer that it went there instead. I dug into the code for zsh-z but, despite thinking I know how to Zsh pretty well, can't figure out how or where to add this.
I was hoping that ZSHZ_UNCOMMON would fix this, but it has different (but understandable) behavior.
I think this option would be great to have but for now, you can always force an exact match by using slashes. So in this case, "z /git/" would give the correct result. In a way, this is just obvious behavior of the matching algorithm, but I thought I'd mention it here for others since it took me about a month before I noticed this
As always, thank you @agkozak for making the pure-Zsh port of Z.
One of the things I tend to butt up against that is that the "frecency" prefers top matches over exact matches.
This might be something to hide behind a non-default environment variable setting, but currently I have:
And if I do
z git
it will go to theshellcheck
directory. Sincegit
has an EXACT match, I'd kind of prefer that it went there instead. I dug into the code forzsh-z
but, despite thinking I know how to Zsh pretty well, can't figure out how or where to add this.I was hoping that
ZSHZ_UNCOMMON
would fix this, but it has different (but understandable) behavior.It would be nice if there was an e.g.
ZSHZ_PREFER_EXACT_MATCHES
setting that would... prefer exact matches.The text was updated successfully, but these errors were encountered: