-
Notifications
You must be signed in to change notification settings - Fork 11
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
Too slow finding files #22
Comments
Originally this had a file cache, but there were a lot of issues with maintaining it. If we go back to a cache we'd need a few things
Locate searches everything, so we could filter the results once we have them, but it only updates daily or weekly and doesn't appear to have a way to force update it. Likely because it's indexing the entire file system. |
I will work on this issue, fileFinder seems cost several minutes to complete, which too long to use without caching. So, I think the cache database is necessary here. How about using |
@twang2218 Right now @afaur is working on a rewrite to make an "adapter" pattern, which should be done this weekend. This should allow more patterns to emerge like the one you are talking about. The issue with the The pattern that @afaur is trying to implement is mdfind (for osx), but once it's done we can also make a |
Since the adapter is merged in now, if anybody wants to make a |
Just curious, this is replacing mdfind with locate right? Is locate really that much faster than mdfind? |
I wouldn't replace |
The command
locate
runs much faster then this plugin.Maybe we can adapt the
locate
command, or maintain a local file index cache?The text was updated successfully, but these errors were encountered: