produces `foo` instead of the desired literal backticks. It appears correctly in the preview however.
This was an actual bug in early versions of the official Markdown Perl implementation
According to the Markdown reference:
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 (
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
If you don't want "foo" in monospace, you can use this:
but then you get spaces around foo.
According to http://daringfireball.net/projects/markdown/syntax#code :
For example, if I can write this: