Stephan Seitz

I'm pretty sure that the problem is what @joshvocal describes. Another possibility is that `C:\Users\PC\AppData\Local\nvim-data\plugged\nvim-treesitter\plugin\` is in your runtimepath. In any case the error is that `require'nvim-treesitter'` picks up the...

It might be possible to add a directive that decides the language based on the macro name (`#inject-macro- lang @_macro`). The directive could have it's own per-languge definition with an...

> I've also been wondering if we could add a directive to remove all other matches on a match. That would allow plugin authors to match specific nodes in the...

@kyazdani42 another idea about revoking queries. We could allow users or plugins to register patterns or regexes and we could filter queries out that contain them. Also your idea of...

@Kasama only works for highlights. @kyazdani42 asked whether we should add this feature.

I think we would need https://github.com/neovim/neovim/pull/17099 Then, we could do something like ```scheme (macro_invocation macro: ((identifier) @macro-name) (token_tree (_)* @macro-args) (#macro-injection! @macro-name @macro-args "rust")) ``` with a config like ```lua...

This is actually the kind of discussion I prefer. For some context. A few highlight groups where added in e2b2d2357. But just there documentation which has the disadvantage that usually...

@ilexite you ran `:PackerCompile` to enable the `config = ...` function?

@UserNobody14 @TimWhiting

Does GDB report a segfault in the parser? Or in Neovim. Best compile Neovim and the parser with debug symbols