Syntax Highlighting for code regions

I happen to have pygments installed, for minted as one does, and with that defaults command written it works quite nicely. As far as I can tell from a quick test anyway.

Somehow I was under the impression you would prefer a fully native option integrated into the markdown system rather than another command line tool, hence the thought on GNU Highlight which recently added on a C++ library interface. Doing it with pygments is certainly good with me though. In fact, pulling in a python-based markdown pipeline would be pretty nice for extensibility (probably dreaming here, but still...).

I'm guessing when you say hardcoded, you mean hardcoded somewhere we outsiders can't really modify. Any chance of a hidden option to switch the style out, or maybe a pointer to how pygments/pygmentize is being invoked so I can interpose something?

Overall this is working great, but there does appear to be a bug in the formatting where the $ character is used. Since lighthouse eats the syntax for breakfast, and doesn't seem to have working verbatim support for backticks, the block bounds are removed below, but imagine the triple-backtick syntax before the language name.

In a bash block like this, the $ and the name after it simply disappear:

bash
echo $meh

Adding a backslash lets it through, but highlights it oddly. Making it a language-free block restores the verbatim semantics to it. Switching it to a non-bash language makes life yet more interesting.

c
echo $meh
echo "$meh"

Putting it in a C language context, as obviously incorrect as the syntax is for C, prints this:

echo $meh
echo ""

So... somewhere there is an odd escaping problem between shell variable expansions and quotes.

Thanks, that was a stupid bug.

I fixed it and it should work in the next update.

Now, I wonder what Lighthouse does with a code segment sent by email:

/bin/bash
echo $meh

<pre><code>
And yes, the style is currently really hardcoded. I&#39;m not sure how it is 
best made configurable. I guess it&#39;s yet another hidden preference. I&#39;ll 
think about it ;-)</code>
</pre>

Hmm, didn't go to well with Lighthouse, but I cannot see that MailMate is to blame.

Thanks Benny!

I apologize if I gave the impression that MailMate was to blame for the Lighthouse issue I mentioned, it isn't. The issue I was running into was that even using the triple-at-sign syntax for verbatim blocks doesn't escape backticks in lighthouse's markup for some reason. As a result, I couldn't put in the exact syntax that was causing issues without spurious and rather odd piles of partially escaped HTML tags, rather like you ended up with. This was actually putting it in through the web form, where a properly escaped version of the bash block I had earlier comes out like this:

```bash
echo $meh

Thanks again for the quick replies, and fixing up the quoting bug for that matter.

Ah, that looks a bit like what happened to my email reply. Maybe it's related.

Testing again:

echo $meh

Maybe it works better with ~~~.

Ok, seems we should use ~~~ and the code styling done by MailMate is definitely lost.

I've executed

sudo easy_install pygments
defaults write com.freron.MailMate MmCodeStylingEnabled -bool YES

Thanks

@dmitry: Try providing the programming language explicitly:

```scala
asasd
```

Since rev 5141 this secret feature seems broken for me ...

The new bundle for this does not appear to work. I have it installed, and the filter programs it installs work if invoked on the command line with appropriate environment variables, but mailmate never seems to invoke them, or install a command to let me invoke them. Is there a trick to making it work, or debug it?

@Tom: Sorry, this functionality is broken until I've finished implementing various features related to handling HTML (including syntax highlighting). I'll have some kind of official beta release when that is complete.

@benny, any news here?

@Tom: If you write me an email then I can point you to a private beta. I'm not quite ready to release it as a public beta/test version. Use “Help ▸ Send Feedback”.