Improve docs/extensions/index.txt #157
Merged
Conversation
This file contains hidden or 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
There was a problem hiding this comment.
I'm using extra in the "Markdown Extra" section below, so let's use something different here.
waylan
pushed a commit
that referenced
this pull request
Nov 4, 2012
Improve docs/extensions/index.txt so that the name for each extension is properly identified.
|
Any chance you can update the online documentation? |
|
And can you please merge one additional small fix (3ea498f62d) from my branch (I don't want to file a new bug for that)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Quoting a comment I got in ReText today:
It seems that it's not clear what extensions names user should pass to Python-Markdown or ReText. Some extensions describe it on their pages, but not all. This pull request aims to improve the situation.