Skip to content
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

Add hard_wrap option for GFM parser #83

Closed
wants to merge 3 commits into from

Conversation

brandur
Copy link
Contributor

@brandur brandur commented Sep 30, 2013

This pull adds a particular option for the GFM parser that specifies whether line breaks should be interpreted as hard wraps.

Fixes #82.

@gettalong
Copy link
Owner

Thanks!

@gettalong gettalong closed this Nov 16, 2013
@brandur
Copy link
Contributor Author

brandur commented Nov 16, 2013

Sweet. Thank-you!

@plexus
Copy link
Contributor

plexus commented Dec 1, 2013

thanks!

antoinealb added a commit to cvra/cvra.github.io that referenced this pull request Sep 11, 2015
GFM is causing issues with the line breaks, replacing every new line
with an HTML </br>, which causes the text to look ugly.

There is a solution to this problem (see
gettalong/kramdown#83) but I could not get it to
work on my machine.

As GFM doesn't bring us significant advantages, and given that
@SyrianSpock and myself use standard Jekyll markdown for our respective
blogs it makes more sense to disable GFM for now.
antoinealb added a commit to cvra/cvra.github.io that referenced this pull request Sep 11, 2015
GFM is causing issues with the line breaks, replacing every new line
with an HTML </br>, which causes the text to look ugly.

There is a solution to this problem (see
gettalong/kramdown#83) but I could not get it to
work on my machine.

As GFM doesn't bring us significant advantages, and given that
@SyrianSpock and myself use standard Jekyll markdown for our respective
blogs it makes more sense to disable GFM for now.
antoinealb added a commit to cvra/cvra.github.io that referenced this pull request Sep 11, 2015
GFM is causing issues with the line breaks, replacing every new line
with an HTML </br>, which causes the text to look ugly.

There is a solution to this problem (see
gettalong/kramdown#83) but I could not get it to
work on my machine.

As GFM doesn't bring us significant advantages, and given that
@SyrianSpock and myself use standard Jekyll markdown for our respective
blogs it makes more sense to disable GFM for now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent hard line break behavior in GFM (GitHub Flavored Markdown) parser
3 participants