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

Jump to bottom

MANUAL: clarify gfm vs markdown_github #4783

Merged
merged 1 commit into from Jul 19, 2018
Merged

MANUAL: clarify gfm vs markdown_github #4783

merged 1 commit into from Jul 19, 2018

Conversation

mb21
Copy link
Collaborator

@mb21 mb21 commented Jul 19, 2018

Hopefully, this wording is clearer? There was at least someone thinking gfm and markdown_github were synonyms. And a few other people asking why gfm doesn't support certain extensions.

@jgm
Copy link
Owner

jgm commented Jul 19, 2018

Looks like an improvement to me.
One thing, though: since the original text was added, we've added support for a few other extensions, besides smart, in gfm; gfm_auto_identifiers, strikeout, pipe_tables, autolink_bare_uris, raw_html, emoji, hard_line_breaks.

@mb21
Copy link
Collaborator Author

mb21 commented Jul 19, 2018

True, it's corrected now.

@jgm jgm merged commit 640814a into master Jul 19, 2018
@mb21 mb21 deleted the mb21-patch-1-1 branch July 20, 2018 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@mb21 @jgm