Bug with Markdown parser

Nicholas Tulach's Avatar

Nicholas Tulach

29 Jan, 2012 03:08 PM

Hey, i found a bug in the Markdown parser. See attached file. The gist is: if you use the '_' method of emphasis followed immediately by a long dash, '—', the Markdown parser doesn't correctly parse the emphasis. Using "*" emphasis works correctly.

See attached example.

  1. Support Staff 1 Posted by Brett on 30 Jan, 2012 10:44 PM

    Brett's Avatar

    I'm not seeing this issue, at least in my dev version. Have you updated to the latest version of Marked? Also, are you creating the long dash directly, or via --- in the original document?

  2. 2 Posted by Nicholas Tulach on 30 Jan, 2012 11:02 PM

    Nicholas Tulach's Avatar

    I am adding the long dash directly. I am using whatever version of Marked is in the Mac App Store.



  3. Support Staff 3 Posted by Brett on 05 Feb, 2012 11:52 PM

    Brett's Avatar

    Sorry for the delayed reply, things got hectic after Macworld.

    The long dash character is probably throwing off the parser. Could you test with --- and see if you have similar issues?

  4. 4 Posted by Nicholas K Tula... on 07 Feb, 2012 02:00 AM

    Nicholas K Tulach's Avatar

    Yeah, that's a workaround.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Already uploaded files

  • test.markdown 57 Bytes

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac