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

Newlines converted to BR tags #63

Open
barraponto opened this Issue Nov 13, 2013 · 2 comments

Comments

Projects
None yet
1 participant
@barraponto

Gist.io is currently converting newlines in markdown to BR tags, but that's not the behavior that Github uses in http://gist.github.com

Examples: https://gist.github.com/barraponto/7450314/ and http://gist.io/7450314

@barraponto

This comment has been minimized.

Show comment
Hide comment
@barraponto

barraponto Nov 14, 2013

This issue stems from the commit 0252440 which starts rendering stuff as GithubFormattedMarkdown. As the documentation says:

In GFM mode, hard line breaks are always taken into account, and issue and user mentions are linked accordingly.

However, I don't see a reason to use such mode as the default. Neither does the Github API, which defaults to regular markdown. Of course, having a context to reference issues, users and commits would be great, provided there was some metadata to inform the Markdown API. Otherwise, it'd be best to stick to regular Markdown.

This issue stems from the commit 0252440 which starts rendering stuff as GithubFormattedMarkdown. As the documentation says:

In GFM mode, hard line breaks are always taken into account, and issue and user mentions are linked accordingly.

However, I don't see a reason to use such mode as the default. Neither does the Github API, which defaults to regular markdown. Of course, having a context to reference issues, users and commits would be great, provided there was some metadata to inform the Markdown API. Otherwise, it'd be best to stick to regular Markdown.

@barraponto

This comment has been minimized.

Show comment
Hide comment
@barraponto

barraponto Nov 14, 2013

Oh and I have to reinforce that regular line breaks in markdown were always ignored, which is great for the 80-chracter-line geeks (like myself). It might make sense for Github textfields, but not for text-editor/code-editor environments.

Oh and I have to reinforce that regular line breaks in markdown were always ignored, which is great for the 80-chracter-line geeks (like myself). It might make sense for Github textfields, but not for text-editor/code-editor environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment