On 14 October 2010 11:25, David Zerrenner <email address hidden> wrote:
> Hi,
>
> I can check that. The bug seems to origin in a faulty call of the
> markdown constructor. Here's a patch that worked for me (Markdown
> 2.0.3):
>
oops, a) sorry for top posting, and b) a diff would've been fine with me :)
On 14 October 2010 11:25, David Zerrenner <email address hidden> wrote:
> Hi,
>
> I can check that. The bug seems to origin in a faulty call of the
> markdown constructor. Here's a patch that worked for me (Markdown
> 2.0.3):
>
oops, a) sorry for top posting, and b) a diff would've been fine with me :)