Flow.Launcher
Flow.Launcher copied to clipboard
Flow-Launcher
Explorer plugin - Everything: Recognize the default filter
Is your feature request related to a problem? Please describe.
When using Everything (1.5a) to search through files and folders, one can use built-in or create custom filters, f.e. to limit search to specific file types, or to only include online volumes. Everything has a built-in filter named "Everything" that is set as default - filtering nothing by default, unless manually specified.
Currently, the default filter is not respected when using the Explorer plugin (with Everything).
Describe the solution you'd like
Add a setting to manually specify a default filter. If empty, use the built-in filter "Everything", or, if possible, detect which filter is set as default in Everything itself.
Describe alternatives you've considered
One has to manually add "filtername:" for every single search, which does not work with the default filter named "Everything", leaving no alternative for it.
I don't think this is possible given the current everything sdk. If you have any idea about how to implement this feature, please feel free to fire a pr or shares an implementation idea.
After further research, accessing filters doesn't seem to be possible currently, but will be added in future.
As an alternative, one could allow the manual creation of filters directly in Flow Launcher. Since filters are a collection of functions, simply concatenated with the search string and passed using Everything_SetSearch, that should be fairly easy to accomplish.
@taooceros What do you think about implementing the manual creation of filters directly in FlowLauncher, as suggested above? Pardon me, if that belongs in a separate issue.
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.
@gisturbance i think you can just concat the filter to your query. Either use a shortcut or a special keystroke shall not be bad.
@gisturbance i think you can just concat the filter to your query. Either use a shortcut or a special keystroke shall not be bad.
Indeed an alternative. For some reason it didn't work for me at the time I created the issue.
However it pollutes the search field, which could be ommited by specifying a hidden default filter.
You can specify a shortcut to simulate that, which might help the pollution?
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh
This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.