Using inline code Markdown (backticks ``) in comments and following it immediately with a non-whitespace character breaks the Markdown causing the backticks to appear and not having the stuff inside the backticks interpreted as code. Strangely this behavior does not appear within posts and answers:

  • With letters: tests
  • With punctuations: test!

It's becoming slightly annoying because a) the behavior is inconsistent and b) I refer to HTML elements as plurals like <br>s and <li>s, and now I have to insert an entirely useless space between them that when read makes it look weird.

Edit As the faq suggest, I should update my post with information on how I attempted to solve the problem myself if nobody takes notice. So, here I am bumping up this post. Oh, and freehand circles:

alt text

As you can see, the new version of Paint included in Windows 7 takes it to a whole new level.

  • tests. See! Its annoying. – Yi Jiang Aug 18 '10 at 13:41
  • 1
    This has been brought up already, but I think the other question should be closed as a duplicate of this, because this is asked better. - meta.stackexchange.com/questions/51417/… – jjnguy Aug 18 '10 at 13:47
  • 5
    These tend to get closed as "[by-design] comment markdown is more limited", for reasons passing understanding – Michael Mrozek Aug 18 '10 at 16:00
  • 1
    Here's one such bydesign ruling. – Grace Note Aug 19 '10 at 12:20
  • My search only brought out the one @jjnguy noted, and that one was just as ignored, old and stale as this one probably will be. – Yi Jiang Aug 19 '10 at 12:36
  • @Michael, it should retagged to [by-sloth] :) – Benjol Aug 19 '10 at 12:42

Can't very well say "no" to freehand circles.

This works now.

| improve this answer | |

You must log in to answer this question.

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