Skip Menu |

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

Report information
The Basics
Id: 68762
Status: resolved
Priority: 0/
Queue: Pod-Cpandoc
People
Owner: Nobody in particular
Requestors: justincase [...] yopmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sat Jun 11 07:59:22 2011 justincase [...] yopmail.com - Ticket created
Subject: Silence perldoc 'no documention found' error message
When a doc is fetched remotely, the error message from Pod::Perldoc is still first displayed on STDERR. Is it possible to catch this with eval and not display if a remote doc is found?
  Sat Jun 11 15:22:11 2011 rt.cpan [...] sartak.org - Correspondence added
On 2011-6月-11 土 07:59:22, justincase wrote: Show quoted text
> When a doc is fetched remotely, the error message from Pod::Perldoc is > still first displayed on > STDERR. Is it possible to catch this with eval and not display if a > remote doc is found?
I want to do this since it's such an obvious failing, but it requires refactoring Pod::Perldoc. Since it's a core module, it's not quite so trivial (but at least I know it'll be maintained). On the other hand, the warning does signal to you that it's going to fetch documentation from CPAN, so it's not entirely bad. :)
  Sat Jun 11 15:22:12 2011 The RT System itself - Status changed from 'new' to 'open'
  Sat Jun 11 21:06:07 2011 rt.cpan [...] sartak.org - Correspondence added
On 2011-6月-11 土 15:22:11, SARTAK wrote: Show quoted text
> On 2011-6月-11 土 07:59:22, justincase wrote:
> > When a doc is fetched remotely, the error message from Pod::Perldoc is > > still first displayed on > > STDERR. Is it possible to catch this with eval and not display if a > > remote doc is found?
> > I want to do this since it's such an obvious failing, but it requires > refactoring Pod::Perldoc. Since it's a core module, it's not quite so > trivial (but at least I know it'll be maintained).
I've released 0.05 which can suppress that spurious warning but only if you have my patch to perl: https://github.com/sartak/perl/commit/5a8c16d4aa82 Until this patch is incorporated in a released perl (or Pod::Perldoc) there's not much I can do to speed this process up for ya. Other than some gross monkeypatching, which I am hoping to avoid. Shawn
  Sat Jun 11 21:06:37 2011 rt.cpan [...] sartak.org - Status changed from 'open' to 'resolved'