This repository has been archived by the owner on Feb 27, 2022. It is now read-only.
Fix: \n should not cause <br> #4
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AFAIK the GitHub readme files are not rendered this way, and it's rather annoying for how I want to use markdown (limit my line length to 80 chars).
|
This project is quite a bit out of date. Github long since moved their GFM implementation exclusively to ruby and do it all server-side, so this project is no longer relevant. The best markdown implementation in JavaScript right now is marked by @chjj. I recommend checking that one out. I believe it supports all the ghm-ism's. |
|
Thanks, created #5 to help others. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AFAIK the GitHub readme files are not rendered this way, and it's rather
annoying for how I want to use markdown (limit my line length to 80
chars).