Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 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

This question already has an answer here:

In the comments on StackOverflow, was misparsed to include the trailing angle bracket. Also there was a semi-colon after it for some reason. See my comment below for an example.

In RFC 3986 Appendix C. Delimiting a URI in Context, three ways are suggested to indicate that a bit of text is a URL.

  1. Angle brackets like <>
  2. Quotes like ""
  3. Whitespace like

Angle brackets are "especially recommended" in the RFC.

Markdown syntax also automatically links angle brackets and SO's editing help mentions it. The comment formatting help doesn't say comments auto-link differently. Comments do auto-link, why do it different?

Thanks for looking. I know free-form URL parsing is a pain, I maintain a library myself.

UPDATE: As you can see in this example -- -- the posting grammar knows how to deal with URLs in angle brackets. Why not in comments? They both do auto-linking. Unless there's some other benefit to the user they should do them the same to avoid confusion. This allows users to learn just ONE set of quirks, not two.

share|improve this question

marked as duplicate by random, Werner, Deer Hunter, Sunshine, Monica Cellio Sep 13 '15 at 21:02

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Here is an example of the comments parsing differently <>; and some filler text. – Schwern Nov 14 '11 at 19:38
To be more clear, the original text is <> which is rendered incorrectly as <>; with the trailing bracket being part of the URL and that mysterious semicolon added. – Schwern Nov 14 '11 at 22:02
Re that mysterious semicolon, see… – balpha Nov 14 '11 at 22:08

The Stack Exchange editor does not use RFC 3986. Instead, the indication that a piece of text is a URL is given by the underlining and color change/mouse pointer change on mouseover.

Linking is done using mini-markdown in comments. Comments only support a subset of markdown, and they do not recommend the use of angle brackets. See the detailed comment help here.

Don't use the angle brackets. Just use the [link]( syntax instead, or allow the URL to be parsed, underlined, and colored differnently.

share|improve this answer
Here is an example of not parsing differently, if you really want your angle brackets: <> produced by [<>]( – Kevin Vermeer Nov 14 '11 at 20:02
Here's an example of a better link to that page: Wikipedia article on inotify, produced by [Wikipedia article on inotify]( – Kevin Vermeer Nov 14 '11 at 20:03
And here's an example of just linking to the page: Can you tell that's a link? – Kevin Vermeer Nov 14 '11 at 20:03
By your first statement, I believe my question wasn't clear. It's not that SO should insert angle brackets when displaying URLs, but that SO should turn URLs with brackets around them into links. This is about autolinking, not display. Otherwise, see my comment to @kiamlaluno's answer, summed up as A) there's no docs saying comments autolink different from posts, yet they do autolink and more importantly B) different autolink behaviors are confusing, why do it? – Schwern Nov 14 '11 at 21:51

Comments use a reduced Markdown set, which is reported in the comment help.


The Learn more link takes you to a page with an extended explanation (it's the section containing "Comment formatting," and "Replying in comments"), but also that section doesn't say that URLs enclosed between < and > are handled in comments.

I would say this is by design.

share|improve this answer
I would say it isn't by design, where's that semicolon coming from? I didn't type it. It doesn't show up with other auto-linked URLs. The comment help doesn't say that autolinked URLs are handled differently, yet it does do some autolinking. And why is it good design to use a different URL autolinking algorithm in the post than the comments? – Schwern Nov 14 '11 at 21:47
It is by design because you are not using something that is supported in comments; if you used <a> tags for links, you would not get the expected result. – kiamlaluno Nov 14 '11 at 22:19
That's a poor rationale for it not working correctly. The comment documentation is obviously incomplete, it does not talk about autolinking at all. More importantly, "it's documented that way" does not explain why it should be that way. Is it in some way more helpful to the user? I suspect it is merely that there are two different implementations of the formatter (one for posts and one for comments) and this slipped by the tests. – Schwern Nov 14 '11 at 23:29

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