Skip to content
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

"EVP_E492: Not an editor command" after escaped bar #98

Open
blueyed opened this issue Jun 1, 2019 · 2 comments
Open

"EVP_E492: Not an editor command" after escaped bar #98

blueyed opened this issue Jun 1, 2019 · 2 comments
Labels

Comments

@blueyed
Copy link
Contributor

blueyed commented Jun 1, 2019

Given:

syn match foo +\(\\\\\|.\)\{-}[^\\]"+

Results in:

t-synerror.vim:1:25:Error: EVP_E492: Not an editor command: ){-}[^\\]"+

It seems to mistake the (escaped) "|" for a command separator (bar) therein.

(seen in Vim's own syntax/vim.vim: https://github.com/blueyed/vim/blob/a4f4d62696782db3aa336e0bc576ddf5263ff36a/runtime/syntax/vim.vim#L310)

@lervag
Copy link

lervag commented May 6, 2021

I've been annoyed at this bug for some time now. I'm curious: Is there an easy way to disable the linter temporarily to avoid this false positive? E.g. something like a comment directive?

@rbong
Copy link

rbong commented Jan 1, 2022

Unfortunate workaround to get this to work in pipelines:

sed -i 's/^syntax .*//' syntax/*.vim
vint .

Or even:

rm -rf syntax/
vint .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants