Skip to content

Add hard_wrap option for GFM parser - #83

Closed
brandur wants to merge 3 commits into
gettalong:masterfrom
brandur:hard-wrap
Closed

brandur wants to merge 3 commits into
gettalong:masterfrom
brandur:hard-wrap

Conversation

@brandur

@brandur brandur commented Sep 30, 2013

Copy link
Copy Markdown
Contributor

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
Copy Markdown
Owner

Thanks!

@gettalong gettalong closed this Nov 16, 2013
@brandur

brandur commented Nov 16, 2013

Copy link
Copy Markdown
Contributor Author

Sweet. Thank-you!

@plexus

plexus commented Dec 1, 2013

Copy link
Copy Markdown
Contributor

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