Exact path matching command line option #980
Conversation
|
Now that it comes to shell integration I don't think I am qualified to progress any further, I do hope this will be somewhat useful if anyone has similar ideas. The added feature is |
|
Your git history is whack since you merged instead of rebasing |
SeeStarz
force-pushed
the
exact-match
branch
from
90baa4b to
2e7b1d7
Compare
|
I completely missed that, thanks! |
SeeStarz
changed the title
| #[clap(long, value_hint = ValueHint::DirPath, value_name = "path")] | ||
| pub exclude: Option<String>, | ||
|
|
||
| /// Only match exact |
There was a problem hiding this comment.
I'd spend a bit more time explaining this feature. This is what will show up in --help
| }); | ||
|
|
||
| if let Some(idx) = idx { | ||
| components = components.drain(0..idx).collect(); |
There was a problem hiding this comment.
This... is convoluted to say the least.
|
Hi it's been a while, average random guy making a PR am i right. Also thanks for reading my PR and reviewing it, and sorry it took so long to reply. Anyways the best feature explanation i came up with while being consistent with others is Upon reconsideration, it's apparent that my implementation doesn't play nicely with any queries with For this reason i'm changing this PR back to draft. My personal interpretation concludes that the easiest way to do so is modifying |
Proof of concept feature improvement related to #260
This adds a new option to allow exact matching of sub path (the ones in between slashes). e.g.
zoxide query rustmatchesrustbut notrust-analyzer. However I haven't been able to understand how to integrate this option into CLI options, as such this pull request isn't complete yet.I personally think just being able to exact match directories would help with QoL especially since the ones most vulnerable to regex matching is short names anyways.
Any feedback would be welcome!