Christian Clason

Yep, can confirm that works! Thanks!

> LaTex supports this syntax Akshually, this is incorrect: This is (plain) TeX syntax, not LaTeX. As this is a parser for LaTeX and not plain TeX (which is _not_...

> TeX syntax is supported I am saying it is not, except where it coincides with LaTeX.

> LaTeX compilers There are no "LaTeX compilers"; there are just TeX compilers that load the LaTeX format by default. But this is nitpicking; it is a design choice that...

@atsmtat could you please test #4280 and confirm whether this addresses your issue? If there's any way you can provide a (simplified, toy) example we could add as a test,...

You are putting the cart before the horse. Neovim is first and foremost a TUI application (that is the _only_ client we ship), so all of this is impossible in...

But this is not how the Neovim project works. _Are_ there any GUIs that even allow for local fonts, no matter how they are specified? Standards are driven by implementation,...

> like 10000 times synchronously But is that a _realistic_ scenario we should consider seriously? I fully accept that `vim.filetype.match` is not performant enough for some use cases (e.g. telescope...

The reason I'm lukewarm (not opposed!) to this change -- as to previous related changes -- is that I'm kinda missing the endgame here. So I worry about a "boiled...

I merely offered this personal note as context to calibrate my comment against. Of course, fixing the current shortcoming with `match` (not all combinations are supported) would be very welcome,...