Christian Clason

Nope, just the output changed -- please ignore.

~~Texlab does not format LaTeX (only BibTeX).~~ Sorry, I spoke too soon: By default, `texlab` calls `latexindent`, see https://github.com/latex-lsp/texlab/blob/master/docs/options.md#texlablatexformatter.

I think I don't want anybody touching my TeX code ;) (I have set the `latexFormatter` to `texlab`, which disables it.) But I would be surprised if `latexindent` doesn't offer...

(page 30 in the manual: set `defaultIndent` to however many spaces you want to use (instead of `\t`, the default value).)

No, that would be `texlab`'s own formatter -- which isn't implemented yet. `latexindent` is an external tool that you need to configure yourself using `yaml` config files.

Maybe, but my comment about `latexindent` being an external tool with its own configuration files still stands.

That's great; I was hoping that these would be rather easy as byproducts of the parsing. Would it make sense to just push any parsing errors straight to diagnostics? Otherwise...

Thank you, that's very interesting to hear. The packrat parser sounds fascinating, really cool! Would you be willing to share the tree-sitter parsers? They might not be competitive for texlab,...

> I think https://github.com/Aerijo/tree-sitter-bibtex/blob/master/grammar.js already does a good job for BibTeX. It just needs to be modified to handle Windows line endings as well but this change should be straightforward....

If you can catch undefined commands or environments, that might be useful?