Christian Clason

Please remove autopairs from the reproducing example. (If you can't, it's an autopairs issue and should be reported there.)

Oh, and don't use lazy. Just clone this plugin and set it up directly.

We have locked the javascript parser before the offending commit, though (but admittedly not the other parsers, if they were updated since then).

Please create a minimal config we can use with `nvim --clean -u minimal.vim` to reproduce the issue.

Does it work if you add empty lines between them? (This is another instance of `@injection.combined` fixing some things while breaking others...)

If you look at `:InspectTree, you see a bunch of parsing `(ERROR)` nodes. Can you give an example snippet that parses correctly and has the same issue?

(Also, Nvim 0.9 is no longer supported.)

> @lsp.type.macro That has nothing to do with tree-sitter. > So does 'Nvim 0.9 is no longer supported ' mean i can no longer get the effect I need? It...

I think we always have to check the metadata; the question is just when (do we precompute that or not); that is the same as for any other query. The...

> Because there are only 15 usages of #offset! and all of them are used to exclude or include some chars, like parenthesis or spaces. In _our_ queries. Experience has...