Provide config to bypass vim autoload #2260
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses some of the user frustration in #2085 and #2071 and is something I've really enjoyed having.
rationale for why I haven't.
actually perform all of these steps.
Why this change is necessary and useful
The current
plugin/youcompleteme.vim
registers the autoload to execute during theVimEnter
stage. But evenVimEnter
must complete before the user can begin editing a buffer. Because of this the YCM vim setup dominates the boot time of even vim configs that leverage dozens of plugins. Executingyoucompleteme#Enable()
can take hundreds of milliseconds even on a modern piece of hardware.This change allows users to disable the default autoloading if they wish so that they can execute
youcompleteme#Enable()
at a more appropriate time and get to an editable buffer faster. It's an advanced user feature, for sure, but I can't think of a better way to allow extremely fast startup time while also using YCM, can you?No automated tests added because the viml doesn't appear to be tested. The change seems to work well, however.
This change is