5

I've just wrote C:\ in a comment and it wouldn't work. I had to write C:\ (with a trailing space).

Am I too drunk, or is it a real bug?

Here on the question it seems to be working.

7
  • This is the workaround: C:\ . And these are bugous: C:` and C:\`. Nov 26, 2012 at 5:39
  • Weird that the comment Markdown works differently than the post Markdown. I want to say this is by-design because it makes sense that you'd want a way to escape the backtick in case your inline code contains a backtick, but it doesn't seem to work that way in posts. I'd almost say the bug is the reverse.
    – animuson StaffMod
    Nov 26, 2012 at 5:54
  • I believe this is by design, as \ escapes whatever is to the right of it, in this case a backtick.
    – user50049
    Nov 26, 2012 at 5:54
  • @TimPost, @animuson: But with two back-slashes it doesn't work either: `C:\`. Nov 26, 2012 at 5:57
  • @desert69 Yeah, that's weird, you'd think `C:\` would work then. I remember this coming up before but I can't seem to find the post that specifically addresses it, it could have been a side conversation on a related post.
    – user50049
    Nov 26, 2012 at 5:59
  • Looks like comments go through different escaping process. Nov 26, 2012 at 7:28
  • @ShaWizDowArd yeap. Surely that's because of the mini-Markup. Nov 26, 2012 at 15:22

1 Answer 1

3

Yeah, comment markdown and escaping is... weird. I've been shying aways from changing this, since it's been like this forever, so it may break a ton of old comments. On the plus side, backslash escaping of backticks in code spans only happens in one-backtick spans*. But since these days, comment Markdown supports Markdown's multi-backtick codespans, you can use that for achieving what you want:

There's something to be found in ``C:\``

*That is a weird sentence.

1
  • Let's see: C:\. Hell yeah :) So this won't be corrected? Thanks, @balpha Nov 26, 2012 at 19:19

You must log in to answer this question.

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