Skip to content
This repository has been archived by the owner on Jan 6, 2018. It is now read-only.

Not any faster than CtrlP's default matcher on big projects #17

Open
patspam opened this issue Apr 25, 2014 · 2 comments
Open

Not any faster than CtrlP's default matcher on big projects #17

patspam opened this issue Apr 25, 2014 · 2 comments

Comments

@patspam
Copy link

patspam commented Apr 25, 2014

On a project with 100k files, searching wasn't any faster for me than when using Ctrl-P's built-in matcher :(

(also, the number of files is hard-coded to a 20k limit)

@burke
Copy link
Owner

burke commented Apr 25, 2014

Sorry, I don't have any projects even remotely approaching that size to develop for. I think you're going to start running into issues where you just can't conceivably handle that much data on a per-keypress paradigm, which is what this ultimately is.

@patspam
Copy link
Author

patspam commented Apr 25, 2014

Speed is my only motivation for installing a custom matcher.

Not to worry, I just found another one that handles 100k files nicely:
https://github.com/FelikZ/ctrlp-py-matcher

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants