Bug with Markdown parser
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.
- test.markdown 57 Bytes
Keyboard shortcuts
Generic
| ? | 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
Support Staff 1 Posted by Brett on 30 Jan, 2012 10:44 PM
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 Posted by Nicholas Tulach on 30 Jan, 2012 11:02 PM
I am adding the long dash directly. I am using whatever version of Marked is in the Mac App Store.
Thanks,
nick
Support Staff 3 Posted by Brett on 05 Feb, 2012 11:52 PM
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 Posted by Nicholas K Tula... on 07 Feb, 2012 02:00 AM
Yeah, that's a workaround.