Open mmktomato opened 2 years ago
So… right of the top, methinks this is a translation issue. Since this was built in legacy vimscript, it was built for legacy vimscript.
Digging…
Digging a bit deeper, my original assumption seems right. Turns out the translation assumes legacy vimscript. If you look at the style/vimspec.vim, you'd realize that the parse_<>
functions — s:parse_describe
, s:parse_hook
s:parse_example
and s:parse_end
— all assume translations into legacy vimscript.
One solution here is to define a vim9script
strategy which could auto-detect on the vim9script
keyword and parse accordingly.
Describe the bug
Vimspec style tests fail in vim9 script.
How to reproduce the problem from Vim startup
Create
test.vimspec
as follows:Then run
./bin/themis test.vimspec
.On the other hand, basic style tests don't fail.
Expected behavior
I expect vimspec style tests don't fail in vim9 script as well as basic style tests.
Actual behavior
See above.
Your environment