"Find in Files" is initially unresponsive when searching a large folder structure
When using the “Find in Files” dialog to search through a large folder structure, the dialog becomes unresponsive right after starting the searching by clicking the “Find All” button.
In my opinion this seems to be the case because when starting the searching first a directory tree seems to be ready fully into memory before actually starting to search at all.
For me this is a bug.
I would love to have a “Find in Files” dialog that is responsive in every stage of the search. I.e. even when initially reading in the the folder structure and not only when later searching inside the actual files.
Here’s some information on filing a feature request or bug report that developers will actually see: https://community.notepad-plus-plus.org/topic/15741/faq-desk-feature-request-or-bug-report
If your intent is to gauge how other users feel about it, you’ve come to exactly to the right place. My feeling: It doesn’t bother me.
There have been similar feelings from other users in the past, and really it comes down to “find should be multithreaded” – and indeed if you search the open issues list you’ll find some like that where you can add your thought (rather than opening an entirely new issue that in the end will just be a duplicate).
OP opened a new issue: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/11774
@alan-kilborn Thank you 😊
As I said, the behavior you seek has been “on the table” for a long time, and nothing has changed. I don’t know that Notepad++ 's limited dev team wants to get too bogged down in searching features, but I have no insight into their thinking.
You might benefit from using an external tool for searching large filesets (allowing you to start a search and then keep working in Notepad++) which can open files in Notepad++ at the match point when the search completes. I don’t know of an ideal tool for this, but GrepWin seems to be a good start…