Various fixes #3
Open
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
This allows vim-grammar to work with dragonfly2.
vim-grammar wasn't working until I did this.
This makes vim-grammar load in Python 2.7 and 3.x without syntax errors.
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.
This PR fixes a few problems with
vim-grammar:Stop requiring the original
dragonflypackage.This lets us use
dragonfly2instead with the same import name.Move all vim sub-packages (i.e.
rules,choices, etc) into a new 'vim' folder.vim-grammarwouldn't work for me until I did this. Let me know if there's a better way.Fix print statements in two files so that they are compatible with Python 3.x.
This just allows
gvim.pyto be loaded under Python 3. There may be other Python 3 specific issues, but I'd need to do more testing.2to3doesn't show anything else though, so that's a good sign! :-)