Return to Question

This is a very minor bug, but I still think it is important to point it out (maybe it was already).

I voted another question to be closed as duplicate of PHP preg_replace the backslash \

Since the title ends with a backslash, the text generated is:

which results in

Though, linking to the question in this question (by just inserting the link) obviously creates an appropriate link. Maybe this automatic link detection / title creation should be done for comments as well, to avoid this issue (which I admit is a minor case)?

(Unfortunately it does not look like escaping the backslash (\\) helps in any way).

Other problematic characters:

• Unescaped ] inside the title.
  As @Konrad points out, it's a problem with Markdown not fully supported in comments. Escaping the slash works well here: php preg_replace \.

• Trailing white spaces. This question has a trailing space in the title, shouldn't those be stripped out?
  Again, this is a limitation of comment Markdown, it works fine here: Link with trailing space .

This is a very minor bug, but I still think it is important to point it out (maybe it was already).

I voted another question to be closed as duplicate of PHP preg_replace the backslash \

Since the title ends with a backslash, the text generated is:

which results in

Though, linking to the question in this question (by just inserting the link) obviously creates an appropriate link. Maybe this automatic link detection / title creation should be done for comments as well, to avoid this issue (which I admit is a minor case)?

(Unfortunately it does not look like escaping the backslash (\\) helps in any way).

Other problematic characters:

• Unescaped ] inside the title.
  As @Konrad points out, it's a problem with Markdown not fully supported in comments. Escaping the slash works well here: php preg_replace \.

• Trailing white spaces. This question has a trailing space in the title, shouldn't those be stripped out?
  Again, this is a limitation of comment Markdown, it works fine here: Link with trailing space .

This is a very minor bug, but I still think it is important to point it out (maybe it was already).

I voted another question to be closed as duplicate of PHP preg_replace the backslash \

Since the title ends with a backslash, the text generated is:

which results in

Though, linking to the question in this question (by just inserting the link) obviously creates an appropriate link. Maybe this automatic link detection / title creation should be done for comments as well, to avoid this issue (which I admit is a minor case)?

(Unfortunately it does not look like escaping the backslash (\\) helps in any way).

Other problematic characters:

• Unescaped ] inside the title.
  As @Konrad points out, it's a problem with Markdown not fully supported in comments. Escaping the slash works well here: php preg_replace \.

• Trailing white spaces. This question has a trailing space in the title, shouldn't those be stripped out?
  Again, this is a limitation of comment Markdown, it works fine here: Link with trailing space .

This is a very minor bug, but I still think it is important to point it out (maybe it was already).

I voted another question to be closed as duplicate of PHP preg_replace the backslash \

Since the title ends with a backslash, the text generated is:

which results in

Though, linking to the question in this question (by just inserting the link) obviously creates an appropriate link. Maybe this automatic link detection / title creation should be done for comments as well, to avoid this issue (which I admit is a minor case)?

(Unfortunately it does not look like escaping the backslash (\\) helps in any way).

Other problematic characters:

• Unescaped ] inside the title.
  As @Konrad points out, it's a problem with Markdown not fully supported in comments. Escaping the slash works well here: php preg_replace \.

• Trailing white spaces. This question has a trailing space in the title, shouldn't those be stripped out?
  Again, this is a limitation of comment Markdown, it works fine here: Link with trailing space .

This is a very minor bug, but I still think it is important to point it out (maybe it was already).

I voted another question to be closed as duplicate of PHP preg_replace the backslash \

Since the title ends with a backslash, the text generated is:

which results in

Though, linking to the question in this question (by just inserting the link) obviously creates an appropriate link. Maybe this automatic link detection / title creation should be done for comments as well, to avoid this issue (which I admit is a minor case)?

(Unfortunately it does not look like escaping the backslash (\\) helps in any way).

Other problematic characters:

• Unescaped ] inside the title.
  As @Konrad points out, it's a problem with Markdown not fully supported in comments. Escaping the slash works well here: php preg_replace \.

• Trailing white spaces. This question has a trailing space in the title, shouldn't those be stripped out?
  Again, this is a limitation of comment Markdown, it works fine here: Link with trailing space .

This is a very minor bug, but I still think it is important to point it out (maybe it was already).

I voted another question to be closed as duplicate of PHP preg_replace the backslash \

Since the title ends with a backslash, the text generated is:

which results in

Though, linking to the question in this question (by just inserting the link) obviously creates an appropriate link. Maybe this automatic link detection / title creation should be done for comments as well, to avoid this issue (which I admit is a minor case)?

(Unfortunately it does not look like escaping the backslash (\\) helps in any way).

Other problematic characters:

• Unescaped ] inside the title.
  As @Konrad points out, it's a problem with Markdown not fully supported in comments. Escaping the slash works well here: php preg_replace \.

• Trailing white spaces. This question has a trailing space in the title, shouldn't those be stripped out?
  Again, this is a limitation of comment Markdown, it works fine here: Link with trailing space .