This is the exact "bug" I joined this mailing list to "report" (having also
used Python-Markdown), and what fueled my desire to see Markdown 2.0.
I do still very much wish we could agree that this really is a bug, as far as
being a completely unexpected result.
Very sad that nothing seems to ch
spencer said:
>"non-pure" Markdown parsers that actually
>work how every person knows it should work
not sure it's 100% "every person" unanimous, but
even 75% (which is 3-1) should carry the day with
a system that's specifically meant to be "intuitive".
-bowerbird
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
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 mailin
