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 often want to run zoxide query --interactive in a large project and have the results all be at the project root where I'm invoking zoxide, not just the ones zoxide thinks are the most popular.
I propose a new --basedir [path] parameter to the query subcommand. If user passes --all we can error out or just preference one or the other. With --list and --interactive it will filter all results for having the same fully qualified path prefix specified by --basedir parameter, with the $CWD being the default value.
The query subcommand already supports an --exclusion mechanism for filtering. This new option to effectively invert that logic will also be valuable. Thanks!
The text was updated successfully, but these errors were encountered:
I often want to run
zoxide query --interactive
in a large project and have the results all be at the project root where I'm invokingzoxide
, not just the ones zoxide thinks are the most popular.I propose a new
--basedir [path]
parameter to thequery
subcommand. If user passes--all
we can error out or just preference one or the other. With--list
and--interactive
it will filter all results for having the same fully qualified path prefix specified by--basedir
parameter, with the$CWD
being the default value.The query subcommand already supports an
--exclusion
mechanism for filtering. This new option to effectively invert that logic will also be valuable. Thanks!The text was updated successfully, but these errors were encountered: