-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Feature Request] Add filter in Favorites #10
Comments
Hi @venkatchand.
I would like to offer you a way to favorite filters.
After selecting one folder in Explorer Panel, execute |
HI @funap, Thanks for your reply. b. On Explorer filter, If possible, List out the file names while keyword typing, without asking file extension. After selecting one folder in Explorer Panel, execute Quick Open from menu -> Plugins -> Explorer. No, After selecting one folder in Explorer Panel, In existing explorer filter, if i want to do filter means i have to give "web*.txt" and hit ENTER to display these files [webcode.txt and webdesign.txt]. What i am expecting is if i type "web" in filter box, it should display the these file names [webcode.txt and webdesign.txt]. Here , we should avoid asking mandatory file extension [*.txt] and hitting ENTER button. |
Hi @venkatchand.
Please try using Quick Open. best regards. |
Hi @funap, Thanks for the clarification. I was used old version of Explorer & thought "quick open" will open file directly, Now understood. Quick Open is what i expected. It would be great if Quick Open works on favorite files and file group [Only searching my favorites files & groups]. If you add this, no need to add filter on Favorites window. (i.e) Quick open for Favorites window. Once again thanks for your time. |
a. On Favorites filter , List out the file names while keyword typing, without asking file extension
b. On Explorer filter, If possible, List out the file names while keyword typing, without asking file extension
Expecting similar feature like this: https://github.com/young-developer/nppNavigateTo
Thanks in advance.
The text was updated successfully, but these errors were encountered: