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
Is there a way to search a file in subdirectories (in any level) recursively?
The default action is searching in the root directory but I can also specify a subdirectory (when I know where the file is located).
The text was updated successfully, but these errors were encountered:
Not right now, no. I'd accept a PR that added the feature provided it can be performant, though.
The idea is close to what the built-in fuzzy-finder provides, except without the "add project folder" step. But adding a project folder helps signal to atom that it should index the project folder for faster searching, which is why it works so fast.
We don't really know at a glance just how deep a subdirectory tree goes, and just having a checkbox to enable subdirectory search would probably lead to a bunch of slowness. We could mark directories as "indexable" with either a button or file in the directory, but I don't like the idea of managing that stored index in perpetuity, nor am I a fan of littering the filesystem with special markers. It'd be neat if maybe we could get access to existing fuzzy-finder indexes, but I doubt that's easy.
@mythmon suggested a special symbol to type in the search box for triggering this kind of behavior, but advanced-new-file had special syntax like that and it wasn't very discoverable or maintainable. He also suggested a keyboard shortcut for switching to a subdirectory search, which isn't a bad idea. It still has the on-the-fly indexing issue, but at least you choose when to do it, so you can avoid doing it in directories that will take too long to search.
Is there a way to search a file in subdirectories (in any level) recursively?
The default action is searching in the root directory but I can also specify a subdirectory (when I know where the file is located).
The text was updated successfully, but these errors were encountered: