Open
Conversation
jesboat
commented
Jan 31, 2013
- Fix GetNextCmd() bugs with dots in strings and other places
- Don't raise errors until the first .v file is opened
- UI tweaks
added 4 commits
January 30, 2013 23:04
In particular, be aware that dots in strings don't end commands, and aware that dots in ".." (e.g. when defining Notation) don't end commands either.
This means people who install the plugin in a ~/.vim/ directory they use with multiple vim versions won't get an error if one vim doesn't support perl or is missing coq if they only use .v files in the other vim.
Shorten it from 70 '='s to only 38. Much more managable.
This file contains hidden or 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
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.