Underscores in words

[SystemParadox]

As described in Github flavoured markdown, it makes no sense to italicise parts of a word.

Underscores in words usually refer to something like a variable or field name so it is particularly bad when these are parsed out and converted to italics.

Please can showdown be changed to use the github rules for this.

Thanks.

[shhQuiet]

Came here to find any issues related to underscores/asterisks/etc embedded in URLs, for example:

![my cat](http://myserver.com/my_kitty.jpg)

This ultimately results in malformed HTML, so I think it's essentially the same issue as mentioned by @SystemParadox

[zachad]

Edit: Just put a backslash in front of the underscore and it will prevent this situation.

[pdeschen]

@zachad thanks for posting the work around!

[tivie]

@pdeschen It's not a bug, it's by design

As described in Github flavoured markdown, it makes no sense to italicise parts of a word.

Showdown is vanilla markdown. As stated in the original specifications:

Emphasis can be used in the middle of a word:

un*frigging*believable

But if you surround an * or _ with spaces, it’ll be treated as a literal asterisk or underscore.

The correct way to prevent the behavior (or to create a literal asterisk or underscore) is to escape it with backslash, as stated in the specs:

To produce a literal asterisk or underscore at a position where it would otherwise be used as an emphasis delimiter, you can backslash escape it:

\*this text is surrounded by literal asterisks\*

[tivie]

Also I could not reproduce the issue @shhQuiet refers to!

Please provide an example where showdown incorrectly parses links and images with underscore so we can have a better understanding of the issue.

[SystemParadox]

Showdown is vanilla markdown

But vanilla markdown is unmaintained and broken in this behaviour. Could an option be added to support github flavoured markdown?

Thanks.

[tivie]

@SystemParadox @pdeschen #164