You nailed it, thanks! =)

This -R option is responsible for the problems on windows since the pager "more" can't handle "-R".

commenting out this line (#1941 for me)

#local $ENV{MORE} = defined $ENV{MORE} ? "$ENV{MORE} -R" : "-R";

fixed the win-bug for me.

Apparently this was added to fix unicode problems on linux, ignoring that Win has it's own "more" pager.

For those who wonder how to find Pod::Perldoc in their local installation

 >perldoc -l Pod::Perldoc
C:\Perl_524\lib\Pod\Perldoc.pm

[download]

does the trick, even with corrupt pager options.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

In reply to Re^2: workaround to fix perldoc (SOLVED) by LanX
in thread workaround to fix perldoc by LanX

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.