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
Please 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 to filter and what follows is the string to filter):
/foo: narrowed list of files containing foo, then: /bar: narrowed list of files containing bar from the already narrowed list of files containing foo
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:
Unlike filter, search does not provide live feedback
filter is usually enough and requires little thought--just type substrings. It's more intuitive, you don't have to consider the order of foo and bar. It's meant to be fast and convenient, whereas search is obviously more powerful using regex but requires more work and thought
searching 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 filters
Would you be willing to contribute this feature?
Yes, I'll give it a shot
Describe the solution you'd like
Currently, filter can only start over the filter from scratch, whether you're using filter or search you can't achieve above without more work and thought. Maybe a filter --smart --continue to insert the existing filter to a new filter.
ESC to exit the filter, Ctrl-L to redraw (refresh) to the screen, going back to the unfiltered state.
Correction: while in the filter (in a /string), Ctrl-l toggles between last filter and currently filtered list. ESC to exit the filter thenCtrl-l will redraw (refresh) to the unfiltered (and updated) list or / to repeated filter on the existing filtered list.
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. /res, ESC, /narESC, /xt to get to this is the result im narrowing for.txt with instant feedback as the list dwindles for better narrowing, along with the possibility to Ctrl-l it at any part of the filtering to start from the previous step again and narrow with a different filter. This is often typed out with no pauses in keystrokes or counting of items thanks to instant feedback (unlike find, which I don't use because it requires more conscious interaction and along with lack of instant feedback makes the workflow slower).
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: