Closed tek closed 3 years ago
even though I have the get_column
fix in my system treesitter, is it possible that neovim doesn't have it yet and therefore exhibits this behaviour when parsing?
matter of fact, there are still those col value outside range
errors in nvim
ping @maxbrunsfeld
ping again @maxbrunsfeld
I don't have very much context on the Neovim side of things, so I think you'll need to figure out:
If the Tree-sitter version is current, and the bug is on the Tree-sitter side, we may need a minimal way to reproduce the bug outside of the context of Neovim.
this is not present anymore in current nvim.
When a semicolon is deduced from indent in the scanner, the next node is skipped when I use tree-sitter for neovim highlighting.
Example:
In this case, only the first line is highlighted, and the second line doesn't even appear in the tree displayed by
:TSPlaygroundToggle
. However, withtree-sitter parse
, it is correctly included in the tree.On the other hand, with an explicit semicolon:
the second line is highlighted as well.
The scanner consumes the newline as part of the implicit semicolon. Maybe that's the problem?
@maxbrunsfeld @patrickt any advice?