I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I use fzf, these days. I always found CtrlP was reeeeeeaaaaaallllyyyy slow in Vim, especially with a lot of files. I'm talking 30 seconds to scan a reasonable-size project. I'm not sure what was holding it up.
Now I use fzf all over the place - I have a bunch of functions and scripts to allow vim or git or whatever to use fuzzy-matching, and use it for things like a fuzzy buffer-explorer inside Vim:
Those look like some interesting features of fzf! Switching to ripgrep for CtrlP's user command has made CtrlP performant enough for me to date.
There was some recent change on my Mac (a brew thing, perhaps?) that caused CtrlP to index my .git directory, which is super annoying. Maybe I'll use that as an opportunity to try out fzf. :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I used CtrlP for some years, it is pretty good.
I've changed to fzf some months ago, maybe you should test it too.
I use
fzf, these days. I always found CtrlP was reeeeeeaaaaaallllyyyy slow in Vim, especially with a lot of files. I'm talking 30 seconds to scan a reasonable-size project. I'm not sure what was holding it up.Now I use
fzfall over the place - I have a bunch of functions and scripts to allow vim or git or whatever to use fuzzy-matching, and use it for things like a fuzzy buffer-explorer inside Vim:I agree, fzf is so powerful, and depending of the Vim version you could have a file preview.
Those look like some interesting features of fzf! Switching to ripgrep for CtrlP's user command has made CtrlP performant enough for me to date.
There was some recent change on my Mac (a brew thing, perhaps?) that caused CtrlP to index my
.gitdirectory, which is super annoying. Maybe I'll use that as an opportunity to try out fzf. :)