Comment form's help text can avoid supersearch perhaps

I was looking for how to insert actual < and > on a comment and saw that under the comment box there is this (tags reducted):

Snippets of code should be wrapped in ... tags not ... tags. In fact, ... tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (... chars), in order to prevent horizontal scrolling (and possible editor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.

But the links either lead to nowhere (1st one) or lead to super-search with no results. Perhaps it can lead to a static page so as to reduce the burden to the site?

bw, bliako

Comment on Comment form's help text can avoid supersearch perhaps

Replies are listed 'Best First'.
Re: Comment form's help text can avoid supersearch perhaps by hippo (Archbishop) on May 12, 2021 at 09:14 UTC
Good spot. I must never have followed those links. I would suggest Linking on PerlMonks for the former and Writeup Formatting Tips for the latter, but almost anything would be preferable to the status quo. 🦛	[reply]
Re: Comment form's help text can avoid supersearch perhaps by choroba (Cardinal) on May 12, 2021 at 09:17 UTC
Interesting. The first link should go to ?node=site+how+to#linking, the second one to ?node=site+how+to#code. (Entered here as `[href://?node=site+how+to#linking]` and `[href://?node=site+how+to#code]`.) Update: Might be related to the latest Tidings from April 16? `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l] [select]
A reply falls below the community's threshold of quality. You may see it by logging in.
Re: Comment form's help text can avoid supersearch perhaps by erzuuli (Cannon) on May 12, 2021 at 13:24 UTC
Thank you! Fixed. Thanks to Corion!	[reply]