Yeah, maybe for v2. The goal of this was to elegantly share .md files (hence the name), so other file types are outside the scope of what I wanted to build.
re:www, it's working on my end: http://cl.ly/image/371J2a1Z2F1s. But I'll investigate.
re:www, it's working on my end: http://cl.ly/image/371J2a1Z2F1s. But I'll investigate.
On yours, as in parent's example, the code blocks don't even get put in a `<pre>`, which would be the minimal 'right thing' if you're not going to do syntax highlighting.
(Of course, yes, syntax highlighting code blocks within .md is pretty much going to use the same logic as handling other file types, it's true).
I guess a clear error message would be helpful, but then you would either have to rely on everyone using standard file endings, or do some pretty fancy (and unreliable) parsing to determine if it's actually Markdown.
One suggestion though: I expect my code blocks to not wrap — they’re in <pre> tags, after all. The stylesheet should have them rendered either with horizontal scrolling, or with overflow.
Compare e.g. http://gist.io/11118629 with http://www.mkdown.com/11118629