Christian Clason

I don't think it makes sense to highlight numbers differently globally -- in LaTeX (or any text markup language), numbers are just part of a text. It would be different...

Looks perfectly fine to me, so the issue must be with whatever queries you are using for this conceal (which are not part of this project).

> Do we actually know who maintains netrw? That's listed at the top of the files: Charles E. Campbell, aka [Dr. Chip](http://www.drchip.org/astronaut/vim/index.html#NETRW) It's still not quite clear what the actual...

> But of course if neovim rather wants to bundle plugins That's exactly what we want to do _less_ of, not more. Your list aptly illustrates why this too quickly...

If you are rewriting the pathlib module from scratch, you should make sure that you are leveraging the latest relevant Neovim API (in particular, `vim.fs`). Plenary was written before there...

Also, a (strong) API design recommendation: 1. **mandatory** arguments should be **positional**; 2. **optional** arguments should be **keyword-style** (i.e., part of a final(!) `opts` table). (This implies thinking hard about...

As LaTeX is whitespace insensitive, the grammar shouldn't be, either.

Yes, and I think this would be the better tradeoff, unfortunate at this is -- unpredictable syntax highlighting (depending on whitespace or not -- and remember that you're not always...

Probably would need a lot more scanner complexity; I don't see how else to deal with this. (And LaTeX is provably impossible to parse and arguably the worst possible language...

This is not enough to repro this; please provide exact steps using `nvim --clean`.