Yes, there is a big difference and the perldoc-style link seems to work well. It would be even better (you just knew that was coming didn't you) if it wasn't case-sensitive or if it redirected to search on failure. Eg: http://search.cpan.org/perldoc?LWP::Useragent simply ends up saying 'Not Found' simply because 'agent' was not capitalised.

Anyway, I've ended up getting sidetracked on the details of linking from PM to search.cpan (which arguably isn't broken anyway) when what I'm most interested in is setting up an infrastructure on PM so that search.cpan can link to discussion forums. I think the best approach (at least initially) would be to base the structure around distributions on the PM side.

In reply to Re*5: search.cpan.org comments/discussion by grantm
in thread search.cpan.org comments/discussion by grantm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.