John Gardner

The scenario you've described is an extremely specific one, and users are assumed to understand the caveats of (ab)using another language's highlighting to improve the readability of their project's source...

This _did_ happen with the V programming language, who classified `*.v` files as Go, as it was both syntactically similar *and* a direct influence on V's design. This was arguably...

> I have to be honest, I've never seen a project be so against adding a feature that would barely require maintenance, while addressing real user problems When I speak...

@Sainan That would actually involve a fundamental change to the way language names and aliases are parsed and normalised (where various forms like `git-config`, `GitConfig` and `.gitconfig` are resolved to...

@lildude Just an FYI, `\G` and `(?!\G)` are two of the most important idioms in TextMate grammars, as they're essentially all authors have by way of maintaining state and structure,...

> in the meantime, we’re moving as many languages as we can to use tree-sitter based highlighting Uh… what languages, exactly? How many? I'm interested in how many of my...

Also, I forgot to ask: _why_ is there an outdated fork of PCRE being used instead of, y'know, something contemporary? This isn't a fault with the TextMate grammar format itself,...

@patrickt Hypothetically, if one were to write a proof-of-concept that demonstrated how TextMate grammars could be used to provide a structured parser grammar based on a combination of their regex...

> but if by “of interest to GitHub” you mean “sufficient for us to prefer TextMate grammars over tree-sitter grammars,” then I’m afraid that the answer is no. No, I...

@patrickt I was _literally_ about to point out how the regression appears to be fixed. Thanks for all your hard work!