My understanding is that ReviewBoard uses Pygments and decides on the Lexer using only the file extension but ".jsm" isn't in the list of extensions for JavaScript. Some options: * try to get ".jsm" added to Pygments * Get https://code.google.com/p/reviewboard/issues/detail?id=2104 fixed in RB and use that downstream * Fix this ourselves for our installation.

Might as well get this upstreamed. https://bitbucket.org/birkenfeld/pygments-main/pull-request/465/detect-jsm-files-as-javascript/

This landed upstream. We'll have to wait for the next Pygments release then deploy it.

I suspect that the syntax highlighting snafus on hg.m.o are the same problem? Is this bug good enough, or should we clone it?

(In reply to Gregory Szorc [:gps] from comment #2) > This landed upstream. We'll have to wait for the next Pygments release then > deploy it. Can we please make our own pre-release build and deploy it? It could be months before a new release as it's already been 10 months since the last one.

(In reply to Matthew N. [:MattN] from comment #4) > Can we please make our own pre-release build and deploy it? It could be > months before a new release as it's already been 10 months since the last > one. Yes.

https://hg.mozilla.org/hgcustom/version-control-tools/rev/1bf62581a350452564653e67d498734554ff9d07 ansible: install custom Pygments distribution (bug 1157502)

hg.mozilla.org and reviewboard.mozilla.org now treats .jsm files as JavaScript. reviewboard-hg.mozilla.org still doesn't because we're installing Pygments from a Mercurial repo and `hg` on this machine has special requirements due to being a special review server and is thus disallowing the repo to be created without a "repoid" config option (needed for review repos). This repoid restriction is kinda silly. But I don't think many people go to reviewboard-hg.mozilla.org, so meh.

Thank you!