Open
Conversation
Author
|
I realize that I'm going to have to make this smarter because |
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.
vspec is a vim testing tool.
It uses vim syntax with additional builtin commands (
describe,it,beforeafter,context).This adds basic support for vspec - that is, by using any of the additional builtin commands vspec will not give an error.
Since this uses
parse_cmd_commonit doesn't actually build the structure of the new blocks. It just treats them as normal commands.I have only added basic support because:
Related issue: Vimjas/vint#330