produces `foo` instead of the desired literal backticks. It appears correctly in the preview however.
Meta Stack Exchange is a question and answer site for meta-discussion of the Stack Exchange family of Q&A websites. It only takes a minute to sign up.Sign up to join this community
This was an actual bug in early versions of the official Markdown Perl implementation
According to the Markdown reference:
The backtick delimiters surrounding a code span may include spaces — one after the opening, one before the closing. This allows you to place literal backtick characters at the beginning or end of a code span
A single backtick in a code span:
A backtick-delimited string in a code span:
Nested backticks with backslash escapes:
Note that the code formatting button does not help here. It changes
How about double back ticks?
Probably have to resort to
This is a proper `backticked piece` without any gray background, or monotype font.
Instead of using `escaped backticks` which look ugly, you can use simple HTML entities, which will not be treated wrongly by the SO server parser. That's a workaround, not a fix of this bug, of course :)
Like so (
` is the HTML Entity for the backtick):
This is a proper `backticked piece`
Inside post comments, you should use the "normal" way, as for some odd reason, HTML entities are written as text in comments:
use \`normal escape\` in comments, HTML entities don't work
According to http://daringfireball.net/projects/markdown/syntax#code :
To include a literal backtick character within a code span, you can use multiple backticks as the opening and closing delimiters:
``There is a literal backtick (`) here.`` which will produce this: <p><code>There is a literal backtick (`) here.</code></p>
For example, if I can write this:
foo`bar like this: