Replies: 1 comment 1 reply
-
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
fzf
is a a fantastic tool, and it's generally fast enough for my purposes. However, in some cases where I'm indexing projects with 10s to 100s of thousands of files, Ctrl+T (or thefzf.vim
equivalent,:Files
) is bottlenecked by the speed of thefind
command used to generate the list of files. As already discussed on #763, this isn'tfzf
's fault at all, and can be fixed by using an alternativeFZF_CTRL_T_COMMAND
.I'm curious what practical recommendations for such a command would be. In particular, when I'm working on machines other than my own (i.e. where I don't have root permissions), I have little control over the
mlocate
database, solocate
isn't an option. What other alternatives do/have people use(d)? One option would be to simply cache a local "database" by running the find command and storing the output to a file, then havingfzf
just parse that file instead of searching. Are there better options? Another good alternative isgit ls-files
(which is bound to:GFiles
infzf.vim
) when working in a git repo.Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions