Christian Clason
Christian Clason
Also `indents` tests might be useful (but not required). Maybe take a look at earlier PRs adding parsers. (Fair warning: I'll hide and/or delete the comments in the near future...
make a PR for it
> I usually only go for the languages to get the parser links and the maintainers but I guess I'm a minority in that regard. Me, too -- that's the...
> Should we uninstall parsers when the install_dir is not in runtimepath? Or is this rather a configuration error? Configuration error. Touching a user's filesystem should be done extremely conservatively...
> But the current detection of the parser via "loadable" status is very buggy. nvim-treesitter will think that parsers that have already been loaded are still installed. I don't see...
Yes, go ahead!
Because you want to update them? (Which is one of the core functionalities of this plugin.)
Can you bisect nvim-treesitter to find out which commit exactly broke highlighting for you? It's very unlikely to be the one you mentioned if you followed the usual advice on...
This is expected since tree-sitter highlighting disables the legacy syntax engine -- which many of these features rely on.
I cannot reproduce that. Please add a _complete_ config I can test with `nvim --clean -u minimal.vim` (see the issue template).