I went and looked at the report and am sad to see that people always use that "remaining pure to Markdown.pl" argument. :(
I'd like to find a single person who *depends* on peculiarities like that and not just anticipates and intentionally works around them when authoring their documents. It's stuff like that which makes it hard to sell Markdown to some of my colleagues. IMHO, as places like Stackoverflow and GitHub implement "non-pure" Markdown parsers that actually work how every person knows it should work, the better off we'll all be. Think of all the time saved not having to explain this over and over. :) Spencer On Wednesday, December 21, 2011 at 7:27 PM, yegle wrote: > Hi list, > > I'm using Python-Markdown and found a potential bug ( or an > undocumented feature? ) > Can anyone confirm this? Thank you :-) > > Bug report on Python-Markdown issue list: > https://github.com/waylan/Python-Markdown/issues/64 > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss@six.pairlist.net (mailto:Markdown-Discuss@six.pairlist.net) > http://six.pairlist.net/mailman/listinfo/markdown-discuss > _______________________________________________ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
