Re^3: Capture STDOUT and send to screen with open3 (updated)

Could you provide a code snipit of how to accomplish?

Something like this maybe?

Update: Now with STDERR support.

use warnings;
use strict;
use IPC::Run qw/ run new_chunker /;

my @cmd = ('yourcommand', 'arg1', 'arg2');
my (@out,@err);
run \@cmd, '>', new_chunker("\n"), sub {
        my $line = shift;
        print $line;
        push @out, $line;
    }, '2>', new_chunker("\n"), sub {
        my $line = shift;
        print STDERR $line;
        push @err, $line;
    } or die $?;
[download]

Comment on Re^3: Capture STDOUT and send to screen with open3 (updated) Select or Download Code

Replies are listed 'Best First'.
Re^4: Capture STDOUT and send to screen with open3 (updated) by karlgoethebier (Abbot) on Mar 06, 2018 at 11:33 UTC
"...provide a code snipit..." Sorry, no. Not in a hurry. I didn't use IPC::Run like this. But haukex gave already some advice. And you are aware that the code you provided at Re^4: Capture STDOUT and send to screen with open3 (updated) doesn't compile? Read more... (2 kB) Best regards, Karl ŤThe Crux of the Biscuit is the Apostropheť `perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'`Help	[reply] [d/l] [select]
Re^4: Capture STDOUT and send to screen with open3 (updated) by computergeek (Novice) on Mar 05, 2018 at 18:10 UTC
I am sorry, I am trying it and it hangs. Here is what I am executing: What am I doing wrong? Also, will this print a line real time from cat as if output were not being captured? `my @cat = qw( cat ); run \@cat, '<pipe', \*PIPE, '>', new_chunker("\n"), sub { my $line = shift; print $line; push @out, $line; }, '2>', new_chunker("\n"), sub { my $line = shift; print STDERR $line; push @err, $line; } or die $?; print PIPE "some input\n"; close PIPE; print "out @out"; print "err @err";` [download]	[reply] [d/l]
Re^5: Capture STDOUT and send to screen with open3 by haukex (Archbishop) on Mar 05, 2018 at 18:20 UTC
IPC::Run's `run` basically runs a command to completion, if you want interactive communication with the subprocess, as your code example appears to be showing, you'll want its `start`/`pump`/`finish` interface. The module's documentation is a bit long, but it is a powerful module, so I recommend reading up on it. Also, a more detailed description of what this subprocess is and what you want to communicate to it would be helpful. Otherwise, if all you want to do is send a single string to its `STDIN`, then I think you should just be able to do `run \@cmd, '<', \$data, ...`.	[reply] [d/l] [select]