Jean Abou Samra

@goshatch Sorry for the long delay, exams and all that. I did a good number of changes everywhere, fixing some bugs (e.g., some regexes were matching over-eagerly), and improving some...

(Pushed a commit to fix line endings, can you configure Git's [core.autocrlf](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration) for the future? Thanks.)

In short, not much. See #2081 for a more recent discussion.

Regarding type annotations improving contributor experience: Please keep in mind that 95% of contributions to Pygments are lexer additions or improvements. Lexers are not large nested pieces of code with...

Please note that we Pygments maintainers aren't experts in hundreds of languages/formats, so we mostly rely on contributions for adding new lexers.

Hm, actually https://w3c.github.io/smufl/latest/specification/font-metadata-locations.html gives this recommendation (unless I'm misunderstanding it?), but it's only explicit for metadata installed on the system.

Some thoughts: - We could make sure every lexer has a `url` attribute, possibly `None`, and check for that in the tests. - We could do something similar with `versionadded`...

Regarding linting: I don't have a lot of experience with that, but I've seen a number of projects (Sphinx, babel) switch to [Ruff](https://docs.astral.sh/ruff). It seems to have gone wildly popular....

> For formatting, if we ever wanted to do that, Ruff is also a good option because it allows selecting single quotes as the preferred style 😄 Lol. I don't...

I think the problem is mostly with word lists inlined into the token definitions that Ruff (or Black) will format with one word per line, right? For these, a solution...