-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add option to use locate? #3
Comments
This could be implemented as another command, for instance |
I think that this would be an absolutely awesome feature. The ideal case would be that telescope-repo creates this cache |
or maybe this cache could be updated on a scheduled basis like once every hour or so? |
The
So, especially in the beginning, I don’t think much integration of the database update with the plugin is needed.
I agree this type of command needs to be fast. It takes less than a second on my machine and that’s almost too much already. |
We may need a bit of refactoring to keep things maintainable even with the |
this is perfect!! |
Working on this, I start to have a solution… |
@molleweide would you be willing to test on your Mac please? (I don’t have one…) |
yeah sure, when I come home later today. |
Use a `locate` command instead of `fd`, to get cached results. Update the documentation as well. Fixes #3
#9 should be ready for your testing when you have time @molleweide . Feel free to put comments there. |
Use a `locate` command instead of `fd`, to get cached results. Update the documentation as well. Fixes #3
Use a `locate` command instead of `fd`, to get cached results. Update the documentation as well. Fixes #3
Use a `locate` command instead of `fd`, to get cached results. Update the documentation as well. Fixes #3
The
locate
command is indexed and could be faster than fd on some machines.Put a 👍🏼 if you are interested in this feature!
The text was updated successfully, but these errors were encountered: