-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using vim-vspec causes "Error: vint: E492: Not an editor command": describe #330
Comments
There's no easy way currently AFAIK - but you could e.g. visually select and manually run Would be nice if this would work however. I think it is not really trivial, since every block would need to be handled as a separate script, and then there's also before/after etc, which would need to be handled together (before/after) the main block (for local vars etc). |
Less-than-ideal workaround for pipelines until vspec support is added:
|
I use vspec (https://github.com/kana/vim-vspec) to test vim functions. DSL Keywords are e.g.
describe
,context
,it
.Filename:
add_debugger_spec.vim
This code produces this error:
Using vim-vspec causes "Error: vint: E492: Not an editor command": describe '#AddDebugger' (see vim-jp/vim-vimlparser)
How could I handle these keywords that is originally no vimscript? Could I add some config to .vintrc.yaml in someway? Could I alternative ignore these files (*_spec.vim) in the vint config file?
The text was updated successfully, but these errors were encountered: