Possible Duplicate:
Markdown italics with underscores look good in preview but not in answer

I just ran into an interesting markdown bug with previews that I thought I'd throw out there in case it's new.

The post in question is here. The text looks fine in the "normal" view, but in the preview pane (while editing) it looks like this:

There's Test::More's eqdeeply() function, which will also display exactly where the structures differ, or Test::Deep's eqdeeply(), which doesn't require a test harness (and just returns true or false).

Somehow the underscore characters are being interpreted as start italics/end italics.

EDIT: I can't seem to reproduce the appearance here. In the preview pane here on meta it looks like it does in the original post, but after posting, it comes out wrong (the asterisks are visible). Clearly it's not possible to demonstrate a bug in markdown using markdown :)


1 Answer 1


Known bug. Intra-word emphasis are part of the markdown spec, but they're disabled here as they cause problems in code snippets.

The bug is that the preview doesn't handle this departure properly, even though it will be correct (for the SO-modified version of "correct") when it's posted. But that's old news:

Not the answer you're looking for? Browse other questions tagged .