Stephan Seitz

`local parser_at_range = parser:language_for_range({cursor[1] - 1, cursor[2], cursor[1] - 1, cursor[2]})` but this will give you the parser at this range. But we want its parent. I also thought about...

@MarkoSagadin there was a recent refactor in the indent queries and the indent module as a whole. Before there would be no indentation on comments as they where handled by...

Can you try how `(ERROR) @auto` will change this behavior in Java. For some languages, this has mitigated the issue a bit. Sometimes one had to apply this rule only...

It depends. We cannot reliable predict what effects errors will have on the parse tree. You could try whether you can somehow make rules on the broken tree or whether...

https://github.com/nvim-treesitter/playground gives you the syntax tree. It might be good to experiment with changes on our tests and add your cases to the test suite.

Maybe error recovery will improve in some situations (https://github.com/tree-sitter/tree-sitter/pull/1635). I don't think the mentioned PR is relevant is this situation but in general there are efforts to improve error recovery....

You need to change the commit in lockfile.json to make CI work.

No, errors are in make highlights *and* injections (invalid node type). Errors only happen in Lua code.

I get these errors  Maybe the revision is wrong? EDIT: ~~aparrently it's `argument` not `arguments`~~ `argument: (_)`

The last time I tried, I could confirm this issue: https://github.com/nvim-treesitter/nvim-treesitter/pull/2407#issuecomment-1025264037 . It's not a blocker for this PR but we should track it in an issue.