In chat and in comments,

[*Felis catus* (domestic cat) Nucleotide BLAST](http://www.ncbi.nlm.nih.gov/ ...)

results in

*Felis catus* (domestic cat) Nucleotide BLAST

not the expected

Felis catus (domestic cat) Nucleotide BLAST

In order to get the expected/desired result, we can mangle the input to something that would make XML cry:

*[Felis catus* (domestic cat) Nucleotide BLAST](http://www.ncbi.nlm.nih.gov/ ...)

This is also a problem if there is formatting at just the end of a link, where

[om nom **nom**](https://www.google.com/search?q=om+nom+nom)


om nom **nom**


[om nom **nom](https://www.google.com/search?q=om+nom+nom)**


om nom nom

  • 2
    +1 XML made me cry a few times, thanks for the revenge hacks! – yannis Jan 11 '12 at 23:34

I've added dashes, brackets, and curly braces to the list of characters that can appear next to formatting delimiters in Mini-Markdown. Since regular parens were already allowed, I don't see why their cornery and wavy brothers shouldn't be. This will work in the next respective builds of chat and the main sites.

| improve this answer | |

You must log in to answer this question.

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