Possible workaround for compatibility hacks depending on plugin load order #86
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To avoid issues with plugin load order affecting compatibility hacks (e.g. where the hack checks for a variable or function only defined after the other plugin has been loaded), move compatibility hacks to autoload and call after other plugins have loaded via VimEnter autocmd.
|
I suspect this isn't going to work reliably with all plugins (because load order also includes load order of autoload files that run functions that immediately makes certain variables useless afterwards; see for example #84, which is just auto-pairs causing problems with itself), but that does not really matter. It seems to work here, and that's what hacks are for :p Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Load plugin compatibility hacks on VimEnter
This is just a suggestion I've quickly put together and seems to work fine.
To avoid issues with plugin load order affecting compatibility hacks (e.g. where the hack checks for a variable or function only defined after the other plugin has been loaded), move compatibility hacks to autoload and call after other plugins have loaded via VimEnter autocmd.