Michel Fortin wrote:
Yeah. That's pretty much exactly what I proposed last year:
http://six.pairlist.net/pipermail/markdown-discuss/2006-October/000349.html
Ahh, forgot that. +1, then.
Also, did anyone notice the syntax John used in this email to denote
code examples?
On 8/3/07, Michel Fortin [EMAIL PROTECTED] wrote:
This is simply because code blocks and the content of a list item
with block-level content are denoted by the same thing: four space of
indentation. To be able to create list items with block-level
Ah, you're right. So this isn't one of the
Maybe this has been reported before, but I can't find it in the
archives.
A code block immediately following an ordered or unordered list
breaks both the list and the code block. Badly.
Tab or spaces for the block don't matter, legal indentation variants
of the list don't matter. Tried a bunch
Jacob Rus wrote:
Unfortunately there has been stiff (not particularly
logical IMO) resistance to formalizing markdown on this mailing list.
I'm not religious about that, but this one did surprise me because I
figured code blocks were tokenized early, since they only get a few
entity transforms.
Le 2007-08-03 à 11:16, Lou Quillio a écrit :
Input:
Some text.
* I am
* a list
I, on the other hand, am a code block. My lines are
indented four spaces.
More text.
