Open
Conversation
When a code span contains backticks, GitHub Flavoured Markdown[1] would not parse it properly unless the surrounding backticks are doubled, or even tripled. Example:
Bad : (1) ` `a` ` (2) ` ``b'' `
Good: (1) `` `a` `` (2) ``` ``b'' '''
[1]: https://help.github.com/articles/github-flavored-markdown
Owner
|
This looks like a quirk in their implementation of Markdown. Pretty much all Markdown implementations do the correct thing here: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%60+%60%60foo%60%60+%60 I'll wait to see what happens with the issue I just filled before I decide what to do with this. |
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
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.
Hi, Michel
You said yesterday you would be interested in what was the Markdown code that didn't parse. It is really minor. You can see the example at the top of
Readme.mdin this commit; if you search for the string "like this", you will see it.You said that you didn't want to rename the files, so I've reverted that.
Kind regards
Jan
When a code span contains backticks, GitHub Flavoured Markdown would not parse it properly unless the surrounding backticks are doubled, or even tripled. Example: