Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

See StackOverflow question "Object Oriented pattern in C ?". When trying to paste a link to a stackoverflow seach that might have helped the asker, I discovered that the comment formater can't handle URLs with '[' in them. Possibly other characters are affected as well.

share|improve this question
Sadly, in the very example you posted, there is a comment with + inside the url working perfectly. – Ian Elliott Jul 29 '09 at 16:54
 wasn't the '+' but the '['...mea culpa – dmckee Jul 29 '09 at 16:55
@Kyle Cronin: Nice. Working. But I don't want to have to translate html entities... – dmckee Jul 29 '09 at 16:56
Wait. Did you just paste that? What browser? I'm using Firefox 3.0.12 on Mac OS. – dmckee Jul 29 '09 at 16:58
@dmckee: I just copied the link in question from your question and pasted it into a comment. It appears that the Markdown (or whatever) auto-escapes the [ and ] in the link. – Kyle Cronin Jul 29 '09 at 17:04
Odd. The one I was complaining about got there after I copied it from the address bar, and pasted into a comment. I wonder what controls it? – dmckee Jul 29 '09 at 17:24
up vote 1 down vote accepted

I know you said you don't want to have to encode the URL, but there isn't really a way around that. The problem is that [ and ] are characters used for signifying links in Markdown. Sure, it could technically ignore [ within a link, but it certainly can't ignore ]. And don't even suggest that it detect pairs of [ and ]; this is a bad idea with regex.

share|improve this answer
Ah. Not east to fix then. Thanks. – dmckee Jul 29 '09 at 17:04
Now you're linking to my site too!? Why not just change your name to Welbog? – JSONBog Jul 29 '09 at 21:09
it is fixed. We force-encode () and [] now – Jeff Atwood Aug 14 '09 at 6:25

You must log in to answer this question.

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