Christian Clason

> when we lock this plugin into what is used in nvim, [...] we seem to be talking past each other -- none of this contradicts what I wrote (to...

Also, a fundamental question: Do we want to put these into the `highlights.scm` queries (following the legacy syntax precedent), or create a new `conceal.scm` query type so people who don't...

I don't know what the best option is, either. For Markdown I agree, but I was mostly thinking of LaTeX. We could also think of handling LaTeX as a special...

No, just the fancy conceals (meaning, you have a replacement instead of just hiding a capture). But there are [a lot of them](https://github.com/neovim/neovim/blob/e9b53f3fb56e91a0d4f15bb36d8068bcc6ea88cf/runtime/syntax/tex.vim#L702-L1223)...

Still the same as I mentioned above: a principled way to opting into levels of conceals (and someone who cares actually implementing all of them).

Note that we have Atom-style fallbacks in Neovim now, so we _could_ add more specific captures in our queries like `@method.call` that fall back to `@method` if the former is...

You can see the list of currently allowed captures here: https://github.com/nvim-treesitter/nvim-treesitter/blob/master/CONTRIBUTING.md#highlights But I think there's a slight misunderstanding: nobody expects you to write _new_ queries for many different languages; just...

This does sound like a sensible approach to me. Part i. sounds like something of general usefulness, so it would be worth (first) investigating what can be done in core...

Can you try removing from your config 1. the empty keys 2. the `module_path` keys 3. the different modules in turn (to see if it's a specific one that errors)?

OK, those definitely should not be in your config, so that is reasonable behavior. Next step: Are you sure the Java parser is actually installed?