Stephan Seitz

@lewis6991 looks nice! Let's see how https://github.com/neovim/neovim/pull/18276 goes. Would be good to stay aligned with upstream :+1:

This is still blocked by the up the upstream PR

I agree with @nickeb96 that `set_query` is not a good solution. `set_query(function..)` would be slightly better since you wouldn't need to load and know everything about the query at start...

I would recommend to read the queries from a file and use the query linter GitHub.com/nvim-treesitter/playground to see what's wrong with your new query. You can also quickly paste the...

@nickeb96 not directly at the moment. You can of course manually read the files from there and then use `set_query`. The disadvantage is that the queries will be loaded when...

This is an error that we observed also in CI for the rnoweb PR. Apparently something has changed with the from Gitlab parsers.

@clason no, it does not require any changes to core. It is already supported but not used in the queries because the current locals implementation is slow (doesn't use the...

@Kavantix use that predicate https://github.com/nvim-treesitter/nvim-treesitter/blob/master/lua/nvim-treesitter/query_predicates.lua#L68 like `(#is? @parameter "parameter")` will check whether the definition of the node is a `@defintion.parameter` in locals for that the captured node needs to be...

From previous discussion about this feature, there was also the wish to have this feature opt-in (even though it should run much faster in future). An easy intro-PR would be...

@ahelwer an efficient algorithm. #1120 was efficient, since there was a cache in tree-sitter to look up `:parent()`. This got now removed and `:parent()` should be avoided. I don't know...