Fix escaping of backtick inside double back-quotes #6371
Merged
Conversation
This file contains 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
|
Great catch! Thank you for this perfect pull request @guilliamxavier! |
xabbuh
added a commit
that referenced
this pull request
Mar 15, 2016
…iamxavier) This PR was merged into the 2.3 branch. Discussion ---------- Fix escaping of backtick inside double back-quotes | Q | A | ------------- | --- | Doc fix? | no | New docs? | no | Applies to | all | Fixed tickets | This PR removes the backslash before the backtick inside a double-back-quoted inline code block, because there it is interpreted literally (and displayed too) instead of as an escaping character. Commits ------- 1c297f9 Fix escaping of backtick inside double back-quotes
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.
This PR removes the backslash before the backtick inside a double-back-quoted inline code block, because there it is interpreted literally (and displayed too) instead of as an escaping character.