> If I can be convinced that perldoc.pl is a better choice for our (PM) needs, I'll switch it.
some thoughts:
- If switching means that old doc-links will refer to perldoc.pl I'm not sure if URL paths are consistent.
- We used to have a [metacpan:://...] alternative to [cpan://..] . ( [docpl://..] might be an option but I'm not too convinced.)
- you may add a user setting such that users like Choroba can choose jumping perldoc.pl for each ... link
Personally I prefer direct auto-linking of bare http-URLs. My wikisyntax does this.
> It was claimed that perldoc.perl.org was moribund,
I only had minor issues with perldoc.perl.org. (like the need to scroll up after a deeplink, because the first lines where covered by the navbar.)
And like already mentioned in the OP are possible deep-targets not easily accessible.
What I have trouble to understand is why they suddenly replaced it with a worse beta-version of something else.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.