-
Notifications
You must be signed in to change notification settings - Fork 546
Repeated filtering like in nnn #2385
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
Comments
Hey @enoryw, I noticed that you did not correctly follow the issue template. Please ensure that:
Issues with |
Correction: while in the filter (in a But yes, fully agree, this feature is a gem and makes working with a TUI file manager actually feel natural. I find even in a long list of items, getting intended results is easy with the context of instant feedback based on search query. E.g. ` |
This is the feature I struggle with most trying to find a comparable alternative in Yazi that's as intuitive and efficient. It feels so natural using in nnn. |
Uh oh!
There was an error while loading. Please reload this page.
yazi --debug
outputPlease describe the problem you're trying to solve
filter
was implemented as a feature supported by nnn/lf/ranger. At least with nnn as a default binding and behavior, you can further narrow down searches, e.g. (where/
is bound tofilter
and what follows is the string to filter):/foo
: narrowed list of files containingfoo
, then:/bar
: narrowed list of files containingbar
from the already narrowed list of files containingfoo
ESC
to exit the filter,Ctrl-L
to redraw (refresh) to the screen, going back to the unfiltered state.I find this workflow to be much faster than
search
because:filter
,search
does not provide live feedbackfilter
is usually enough and requires little thought--just type substrings. It's more intuitive, you don't have to consider the order offoo
andbar
. It's meant to be fast and convenient, whereassearch
is obviously more powerful using regex but requires more work and thoughtsearch
ing the filesystem is expensive and in-efficient when you're continuously adjusting to get the results vs. simply narrowing down a narrowed list with repeated filtersWould you be willing to contribute this feature?
Describe the solution you'd like
Currently,
filter
can only start over the filter from scratch, whether you're usingfilter
orsearch
you can't achieve above without more work and thought. Maybe afilter --smart --continue
to insert the existing filter to a new filter.Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: