Skip to content

typing in index several seconds for 1 letter #331

Closed
dezza opened this Issue Dec 17, 2012 · 5 comments

3 participants

@dezza
dezza commented Dec 17, 2012

I have tried to use a vimrc without anything but nocompatible and runtime ! plugin/ctrlp.vim

If I type anything to search through the filelist (the one that comes up pressing CTRL+P by default) it slowly types and searches with several seconds for 1 letter appearing ...

I know there already is a closed issue, but I thought you should know, since I've narrowed it down to really being a problem with the plugin itself or gVim for Windows - I didn't include mswin.vim optimizations or behave mswin, but I tried earlier with it, and also tried various other combinations.

Can only get this to run fast on Linux at the moment.

@kien
Owner
kien commented Dec 17, 2012

Which closed issue do you refer to? But this slowness is typically because ctrlp can't handle the large file list. This is slightly more apparent on Windows. There's really nothing I can do about it other than to tell you to try limiting the number of files with the g:ctrlp_max_files option, and updating ctrlp and gVim.

@kien kien closed this Dec 17, 2012
@dezza
dezza commented Dec 17, 2012

Seems similar to these issues:
#331
#46
#55
#116

@kien
Owner
kien commented Dec 18, 2012

Have you read them or just put up everything you could find after I asked?

#46 wasn't a bug. It was a delay when starting up caused by the user having similar mappings.
#55 I even asked the person in another issue but he never provided the file that caused it.
#116 was fixed. It was fnamemodify() being slow, the same reason I've always tried to avoid using this function.
#331 is this issue.

Also, I want to add that I see every issue as something that I need to deal with, to be done. I will close and ignore the ones that I deem not worth following up, they may or may not be actual fixable bugs. But if there's a valid bug or a common problem I can identify, I always try to fix it or at least provide a solution for it as soon as I see the report.

@chevex
chevex commented Mar 4, 2014

I think I'm suffering from the sheer number of files as well. I'm working in a huge repository and depending on my search, it sometimes takes seconds to even display the letters I'm typing, let alone the results I'm looking for. This is only for certain searches though.

I also have a problem with a couple files not being found at all, but if I search from a lower-level directory (where I know these two files that won't show up would be the only ones CtrlP could find) then it finds them. If I search from the higher-level directory it finds a file with the same name in a different subdirectory but not the files in the other.

I will try setting the g:ctrlp_max_files variable and see if that helps. Is there a comprehensive list of CtrlP settings? It seems like I've discovered several settings by encountering issues and then Googling for them, finding the same issue in the issue tracker, and then seeing new variables I can use that I've never seen in the documentation. If you wouldn't mind adding a comprehensive list of these variables in the README I think it would be tremendously useful :)

@kien
Owner
kien commented Mar 5, 2014

CtrlP has a documentation which you can access by running :help ctrlp.txt. All the available options are documented in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.