Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Capture-Tiny CPAN distribution.

Report information
The Basics
Id: 60515
Status: resolved
Priority: 0/
Queue: Capture-Tiny

People
Owner: Nobody in particular
Requestors: bdfoy [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Can we have capture_stdout and capture_stderr?
I'd like to have capture_stdout and capture_stderr so I can choose to get only one of them. I don't need it right away so I don't have the patch, but I can see wanting this the next time I need Capture::Tiny. :) I don't particularly care about the names.
Subject: Re: [rt.cpan.org #60515] Can we have capture_stdout and capture_stderr?
Date: Thu, 19 Aug 2010 09:48:14 -0400
To: bug-Capture-Tiny [...] rt.cpan.org
From: David Golden <dagolden [...] cpan.org>
On Thu, Aug 19, 2010 at 8:32 AM, brian d foy via RT <bug-Capture-Tiny@rt.cpan.org> wrote: Show quoted text
> I'd like to have capture_stdout and capture_stderr so I can choose to get only one of them. I > don't need it right away so I don't have the patch, but I can see wanting this the next time I > need Capture::Tiny. :)
I've heard that before, so I may look into it sooner rather than later. I hadn't realized there was so much need for it. David
On Thu Aug 19 09:48:41 2010, DAGOLDEN wrote: Show quoted text
> I've heard that before, so I may look into it sooner rather than > later. I hadn't realized there was so much need for it.
Did anything ever happen with this? I'd also really like to see this feature. If one is using, for example, Log4Perl to do things to STDOUT and you have a block of XS STDERR stuff to capture so you can then log with Log4Perl, you don't necessarily want to capture also all STDOUT and then have to work out later whether you need to $logger->warn or $logger->info etc. for each caught line of STDOUT - I'd rather leave all that alone and just get stderr.
On Thu Aug 19 09:48:41 2010, DAGOLDEN wrote: Show quoted text
> I've heard that before, so I may look into it sooner rather than > later. I hadn't realized there was so much need for it.
Did anything ever happen with this? I'd also really like to see this feature. If one is using, for example, Log4Perl to do things to STDOUT and you have a block of XS STDERR stuff to capture so you can then log with Log4Perl, you don't necessarily want to capture also all STDOUT and then have to work out later whether you need to $logger->warn or $logger->info etc. for each caught line of STDOUT - I'd rather leave all that alone and just get stderr.
Subject: Re: [rt.cpan.org #60515] Can we have capture_stdout and capture_stderr?
Date: Sat, 15 Oct 2011 14:01:41 -0400
To: bug-Capture-Tiny [...] rt.cpan.org
From: David Golden <dagolden [...] cpan.org>
On Sat, Oct 15, 2011 at 11:28 AM, Philip Kime via RT <bug-Capture-Tiny@rt.cpan.org> wrote: Show quoted text
>       Queue: Capture-Tiny >  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=60515 > > > On Thu Aug 19 09:48:41 2010, DAGOLDEN wrote: >
>> I've heard that before, so I may look into it sooner rather than >> later.  I hadn't realized there was so much need for it.
> > Did anything ever happen with this? I'd also really like to see this feature. If one is using, for > example, Log4Perl to do things to STDOUT and you have a block of XS STDERR stuff to capture > so you can then log with Log4Perl, you don't necessarily want to capture also all STDOUT and > then have to work out later whether you need to $logger->warn or $logger->info etc. for each > caught line of STDOUT - I'd rather leave all that alone and just get stderr.
Not yet. It's in my "get to eventually" queue, though. :-) -- David
Released to CPAN in Capture::Tiny 0.012