Open trendels opened 9 years ago
Thanks for the heads up.
I also think there might be some issues with some regexes with include an engine selector, which I also think 7.3 lacks, but I'm not sure.
I have pushed a syntax file with some changes to the 7.3 branch, please confirm if that solves the issues under 7.3. I decided againts introducing version checks into the main syntax file because that will clutter things up. I'm not yet decided what the best strategy forward should be.
That said, I would suggest to update vim if at all possible, because 7.4 has significant performance improvements relevant to syntax files.
Hi, the errors are gone when using the 7.3 branch. Thank you for the quick fix.
Not sure what to do about the version support. Vim 7.3 will probably be around for a while, due to it being shipped with an LTS release. Personally I don't mind upgrading vim, but so far it's the only time the version has been a problem (otoh, I don't use a lot of extensions to begin with).
7.3 is also shipped in OSX, if i remember correctly, so this is a concern.
I can confirm that OSX ships with 7.3, and this error occurs for when when using the stock Vim on this platform as well.
I wonder if it would be possible to have a top-level conditional, e.g.
if v:version >= 704
" the master/currently-maintained definitions
else
" legacy definitions
endif
It will be ugly, maybe. But the legacy definitions do not need to be updated maintained (very much). It will just be a snapshot of the 7.3 branch. Right now, it is very difficult to use this plugin if you are forced to use different versions of Vim in different contexts (e.g., remotely on a cluster vs. at work vs. at home) and they all share the same configuration repo. The above hack will at least avoid the cascade of errors on-startup when using older Vim's.
Apologies if this is already known. Vim 7.3 (which ships on Ubuntu 12.04 LTS) has +conceal, but doesn't support the
\@1
syntax in regular expressions.vim --version
:Loading the syntax file produces: