Correct markdown highlighting of <>& and fenced code bocks #23
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
The html syntax that this inherits from highlights unmatched triangle braces (<>) and also & as errors. (& should be &) They are however escaped by markdown so this stops tham form showing.
Fixes highlighting around line 70 of the Markdown index page source. (http://daringfireball.net/projects/markdown/index.text)
This code comes from https://gist.github.com/1034258.
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Two little commits that add support for fenced code blocks and also clear the error highlighting that occurs in html on unmatched angle brackets (<>) or on an unescaped &, these are fine in markdown as they get escaped automagically.