Loade plugin keymaps and settings in correct order #468
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
Enabling to load plugin keybindings and settings in order also adding them into editors settings|keybindings hierarchy
|
Probably because the current version uses API calls that lime does or did not support. Or maybe just so that there was something to work with that wouldn't change constantly. |
zoli
added a commit
that referenced
this pull request
Dec 8, 2014
Loade plugin keymaps and settings in correct order
Because we were referencing the lime2 branch, but it appears that the move to from 3rdparty -> packages incorrectly made it reference master. I don't see how that even can work and looking at the travis build it looks to me like the Vintageous tests aren't actually running at all which might explain why they don't explicitly fail. |
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.
Now Vintageous plugin works properly on front ends closes #467.
BTW why we're using Vintageous fork?