Closed justinmk closed 1 year ago
@justinmk can we get this in for 2.0.0/Nvim 0.9, even as a partial fix? Seems like the code should work?
Why is this a priority for nvim 0.9? AFAIR this change wasn't as easy as it looks, though I can try to look at it in a few days
Not a priority, just nice to have (and marked as a breaking change, so could be rolled into the 2.0.0 release).
This is in decent shape now and fixes #96 .
✅ It causes some errors in the generated help, need to double-check that.
any follow-ups planned? otherwise I'd cut a release and bump the bundled parser.
Yeah I think we should get https://github.com/neovim/tree-sitter-vimdoc/pull/103 in before releasing.
That one has a bunch of regressions, unfortunately. I'd prefer to tackle this in smaller steps, fwiw. Let's see how it looks after a rebase, though.
Yeah, no objection to releasing.
Release early, release often ;)
(I'm trying to poke tree-sitter into making more regular releases from their parsers; right now, we're either stuck in 2021 -- worst timeline -- or need to track HEAD even for releases.)
In any case, not really urgent; that was meant more as an offer to take things off your plate.
Problem
(argument)
supports whitespace but,{
is used in textSolution
(argument)
fixes https://github.com/neovim/tree-sitter-vimdoc/issues/96