Skip Menu |

This queue is for tickets about the Pod-Perldoc CPAN distribution.

Report information
The Basics
Id: 85173
Status: resolved
Priority: 0/
Queue: Pod-Perldoc
People
Owner: Nobody in particular
Requestors: gfuji [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Critical
Broken in: 3.20
Fixed in: (no value)

History Show all quoted text
  Thu May 09 22:38:53 2013 gfuji [...] cpan.org - Ticket created
Subject: RT #69380 (commit a0da12a8d6caf728fb3da207d399d14727933fb2) breaks my use
Hello, RT #69380, changed use of PERLDOC_PAGER to reading buffer from stdin, has broken my use: `PERLDOC_PAGER=vim perldoc -m module`, my favorite way to read a module source code. I'd like to revert that change to keep backward compatibility. If #69380 must be fixed - I don't think so, though, because it's easy to set PERLDOC_PAGER="foo <" - you'd better make a new configuration env like PERLDOC_PAGER_FROM_STDIN. Best Regards, -- Goro Fuji (gfx) GFUJI at CPAN.org
  Fri May 10 18:55:44 2013 tsibley [...] cpan.org - Correspondence added
On Thu May 09 22:38:53 2013, GFUJI wrote: Show quoted text
> I don't think so, though, because it's easy to set PERLDOC_PAGER="foo <"
Is PERLDOC_PAGER="vim -" not just as easy?
  Fri May 10 18:55:45 2013 The RT System itself - Status changed from 'new' to 'open'
  Sat May 11 08:22:32 2013 gfuji [...] cpan.org - Correspondence added
On Fri May 10 18:55:44 2013, TSIBLEY wrote: Show quoted text
> On Thu May 09 22:38:53 2013, GFUJI wrote:
> > I don't think so, though, because it's easy to set PERLDOC_PAGER="foo <"
> > Is PERLDOC_PAGER="vim -" not just as easy?
I see, thanks. However, there are various versions of perldoc I use. How can I write shell setting to handle perldoc's incompatibility? In fact, my setting worked for a decade until #69380 broke it. If perldoc was not a core module, I wouldn't say anything, but it's a core module. It must not break compatibility. -- Goro Fuji (gfx) GFUJI at CPAN.org
  Tue Jun 04 10:13:52 2013 mrallen1 [...] yahoo.com - Correspondence added
On Sat May 11 08:22:32 2013, GFUJI wrote: Show quoted text
> On Fri May 10 18:55:44 2013, TSIBLEY wrote:
> > On Thu May 09 22:38:53 2013, GFUJI wrote:
> > > I don't think so, though, because it's easy to set
> PERLDOC_PAGER="foo <"
> > > > Is PERLDOC_PAGER="vim -" not just as easy?
> > I see, thanks. However, there are various versions of perldoc I use. > How can I write shell setting to handle perldoc's incompatibility? > > In fact, my setting worked for a decade until #69380 broke it. If > perldoc was not a core module, I wouldn't say anything, but it's a > core module. It must not break compatibility.
The way I'm approaching this is to have a special pager environment variable PERLDOC_SRC_PAGER when the "-m" flag is used on the command line which does not redirect STDIN. The previous perldoc behavior you relied on actually does not match the documentation, and that's why the behavior was changed.
  Tue Feb 04 22:55:11 2014 mrallen1 [...] yahoo.com - Correspondence added
On Sat May 11 08:22:32 2013, GFUJI wrote: Show quoted text
> How can I write shell setting to handle perldoc's incompatibility?
I added support for a special environment variable PERLDOC_SRC_PAGER which takes precedent when perldoc is in the -m mode. It's on github now as commit 58ff530 - should be on CPAN in a few days.
  Tue Feb 04 22:55:12 2014 mrallen1 [...] yahoo.com - Status changed from 'open' to 'patched'
  Thu Jul 28 12:39:27 2016 mrallen1 [...] yahoo.com - Status changed from 'patched' to 'resolved'