Stephan Seitz

Nice idea to use -xc to convince g++ to compile C. You might also try https://github.com/nvim-treesitter/nvim-treesitter to compile parser binaries for more languages or export the compile commands for additional...

Is it only for `tree-sitter parse` or `tree-sitter query`? If query which query file are you using can the file be reduced to a minimal example?

Just use a few lines of this query file. Try to determine whether the first half of this file is slower as the second half.

@ubolonton The directive takes to nodes and creates a data structure describing the range from the beginning of the first node to the end the second node and stores them...

@meain please not that `make-range!` was created just for the needs of nvim-treesitter-textobjects since there is no obvious way to select multiple nodes using tree-sitter queries. It was not adopted...

Grouping sibling nodes only allows you to specify a order of the nodes. It would allow you to set a capture on each and every of the mentioned subnodes on...

Other comment, in the original issue commenf the implemention of make-range is linked. This is kind of misleading if how predicates/directives work today in Neovim. This legacy predicate is still...

This is the PR which would fix that we can have multiple nodes per capture and match: https://github.com/neovim/neovim/pull/17099. Right now you can register predicates and directives: https://github.com/theHamsta/neovim/blob/3b0a0c6ca6c5f4e719028be2dba11853ffec6b6b/runtime/lua/vim/treesitter/query.lua#L347-L371 they work then...

`@function.outer.start` are optional decorations for the textobject like doctrings or template declarations. They will be added to the textobject range if present.

At the moment we have **no treatment of whitespaces** at at all in this plugin. I always wanted to do this finally but I've never come to point to actually...