@R.M. You mentioned before that it's not difficult to hack Pygments to use your highlighter even for mma (and not only wl). Could you give some more details on that? (Note I haven't set this up yet ...)

@R.M. Actually I think I'll just stick to wl.

@halirutan Did you actually get pygments and pygments-mathematica working with Pelican?

@R.M. Does it look right to you to get error highlighting on this with pygments-mathematica?

I'm trying to use it with Pelican. How can I verify that it really is using the correct highlighter? I tried wolfram and wl, both give the same.

mma gives something different, I guess that's the builtin Mathematica highlighter.

Invalid names give no highlighting, as expected.

@halirutan One problem is I cannot get it to output the correct class (language-wl or similar) ...

@Szabolcs Yes I got it working.

@halirutan You get the language name output as a CSS class too?

The problem is that there is no way when you write markdown to annotate that mma should be used. So you need to set the language-wl class globally.

Very annoying.

I can look up my config at home and post it later if you like.

Ah, I see ...

@halirutan Do you also have problems with many non-errors being highlighted as errors, like above?

@Szabolcs Not that I know of, but I can test this.

blog.liang2.tw/posts/2016/02/markdown-codehilite-lang

@Szabolcs Exactly. Without adjusting the python code it is not possible to send the language class down to where pygments is called.

@Szabolcs Hmm... I see that as well. I must've missed it because I set the style for .err to be a default gray/black instead of a red box, so it doesn't stand out. I'll look into this today/tomorrow (Please open an issue on Github)

@Szabolcs This is now fixed. (both in pypi and github)