Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TorgoX (1933)

TorgoX
  sburkeNO@SPAMcpan.org
http://search.cpan.org/~sburke/

"Il est beau comme la retractilité des serres des oiseaux rapaces [...] et surtout, comme la rencontre fortuite sur une table de dissection d'une machine à coudre et d'un parapluie !" -- Lautréamont
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • On the pod-people list you annouced:

    One note about the current dist: since this is just an alpha release, it doesn't replace your perldoc executable, but instead gives you a new executable called "perldoc3". So don't try using the new options with your old perldoc.

    What exactly are the new options? I didn't yet find any difference (except for the removal of the annoying taint-checking thing when being root).

    Oh, just noticed that: something odd has happened to the -i switch. Doesn't work for my any lon
    • Whoops, I just realized I forgot to list the new options in the usage screens. It's in "perldoc3 perldoc3" tho. Notably: -T terminal

      This specifies that the output is not to be sent to a pager, but is to be sent right to STDOUT.

      -d destination-filename

      This specifies that the output is to be sent neither to a pager nor to STDOUT, but is to be saved to the specified filename. Example: perldoc -oLaTeX -dtextwrapdocs.tex Text::Wrap

      -o output-formatname

      This specifies

      • Whoops, I just realized I forgot to list the new options in the usage screens. It's in "perldoc3 perldoc3" tho. Notably: -T terminal

        Ah, great! I can directly perldoc into a vim buffer finally or somewhere else(for ease of further processing). Very nice!

        I'll think I just add an alias to make perldoc3 a replacement for the current perldoc. Thus, possible bugs should show up most quickly if any.
        • Ah, great! I can directly perldoc into a vim buffer finally or somewhere else(for ease of further processing). Very nice!

          That should have worked before (without the explicit -T) -- but sometimes didn't. Now you can use -T to make totally clear "no pager!!".

          I'll think I just add an alias to make perldoc3 a replacement for the current perldoc. Thus, possible bugs should show up most quickly if any.

          Wow, thanks! I'll be sure to post news, here in my log, of any new Perldoc versions.

  • Thanks there Mr. X. I have installed it and will let you know how it all pans out. Anything you'd particularly like tested? The new output formats? Are you using any bug tracker software?
    • Nope, I'm not using any particular bug-tracking software; just email me any reports of trouble.

      As to what to test: anything and everything -- the whole thing is either all new, or newly refactored. Like someone just told me "-i" isn't working anymore, which I didn't notice because I've been using MSWin, where it's a no-op. I don't remember messing with the "-i" code, but I'll have a look at it now.