According to 43037 shortcuts should be available for But while the first one indeed does work, it seems to me that doc:// only links directly to functions, and I think it would be desirable to have a shortcut to directly link say modules, also because if you think about it from the point of view of the cmd line UI it is that form of perldoc that is in some sense the most straightforward.

Example: [doc://Benchmark], which indeed is not what intended and IMHO doesn't match well with 'perldoc Benchmark'.

Replies are listed 'Best First'.
Re: About [doc://] and [perldoc://]
by demerphq (Chancellor) on Feb 02, 2005 at 13:53 UTC
      D'Oh! Obvious... well, it's obvious now that you point it out to me!! Thank you very much.
Re: About [doc://] and [perldoc://]
by davido (Cardinal) on Feb 03, 2005 at 00:02 UTC

    ...it seems to me that doc:// only links directly to funcitons...

    Not exactly. It works like this: If the document name starts with "perl..." it assumes the document is not a function, but instead a piece of the core POD (but not a module or pragma). If the name doesn't start with "perl..." it assumes it's a function and attempts to link that way instead.

    As demerphq mentioned, if you're looking to link to a module or pragma, use [cpan://Modulename].

    Examples of proper use of [doc://......] include:


    Dave

      Thank you very much for the further details. Actually I was about to answer that the above referenced portion of the faq is slightly deceiving in that really only functions can be directly linked to. Now I realize that this is not the case, but I have them impression it's still slightly deceiving (even if much more slightly) and that maybe it could be advantageous to pinpoint there the same details hinted to here. Unless they're already there and I'm just missing something obvious...