-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference links following lists are inlined #77
Comments
Bah, good catch. This is actually a part of a trickier problem. There are some easy fixes for this, but none that actually replicate exact markdown.pl behavior. I really do want to replicate markdown.pl exactly here, but I'll have to find an efficient fix. |
This was a little bit tricky to fix and I'm still not happy with it, but for now, this works: 48c6a43 |
The 48c6a43 commit does not seem to be ever merged to the master, and thus the latest npm-hosted marked (version 0.2.8) still does have this issue (if Is that because you are still not happy enough with the fix? |
@chjj What's holding this up? |
+1 for this issue would be nice to have support for this. By the way thanks for the great work @chjj ! |
Given the following document:
marked
renders:... whereas I'd expect:
GitHub's markdown parser seems to get it right (live preview):
link
The text was updated successfully, but these errors were encountered: