Stephan Seitz

Superseded by #343

@amaanq upstream has updated to expose `$._match_block` as `$.block`. This was the original intention of this PR. In the official Python grammar, this special case of block is called a...

The unnecessary conflict can still be removed.

tree-sitter-yaml has a c++ parser. There could be a problem with loading the C++ runtime. Could you check via https://github.com/lucasg/Dependencies what DLLs `yaml.so` would load (in reality it is a...

> > should vim.treesitter.query.get be cached? > > Correct me if I'm wrong, but doesn't core already cache this via a weak table? I believe you're right, they should be...

 Really weird surprisingly similar to https://github.com/nvim-treesitter/nvim-treesitter/issues/1371

It seems that all queries with `@_foo` match now automatically, as if `@_foo` wouldn't be there. ``` ;((environment ;(begin ;name: (word) @_frame) ;(brace_group ;child: (text) @text.title)) ;(#eq? @_frame "frame")) ;((generic_command...

Is the same issue as for html. I posted the culprit queries for htmls.

@winston0410 while you're waiting for documentation, you could have a look on how mini-grammar extension like json-> json with comments, C++ -> CUDA work https://gitlab.com/WhyNotHugo/tree-sitter-jsonc/-/blob/main/grammar.js https://github.com/theHamsta/tree-sitter-cuda/blob/master/grammar.js Add the base parsers...

I'm not sure but I guess all the built-in functions of the Tree-Sitter DSL are provided by the Rust code generating the grammar.