Ok, now you are getting to the nitty-griity of your original problem. You need to realize that the shells created with IPC::Open3 use automatically generated pipes to communicate the data. Pipes act differently than you might expect, and it is sometimes requires some code trickery to read them in realtime. Otherwise, the pipe must be closed to force it to flush out all it's data.

So, your problem was

#getresult while(<OUT>){......}
Since OUT is connected to a pipe, you can never leave the loop until it closes, and it never closes with a bash shell (but it will with a simple command).

So, you need to get rid out the while(<OUT>) syntax, and switch to sysread. Something like this:

if( sysread( OUT, my $buffer, 2048 ) > 0 ){ print $buffer }
The above sucks 2k from the pipe, until there is 0 there. Be warned however, that this is not a general purpose solution to the problem. Each command can act differently, and there are a whole bunch of uncooperative commands that require a terminal to output to. These commands need a pseudo-tty ( see IO::Pty ) and can be very hard to deal with.

But for most commands, a combination of IO::Select and sysread will work. Here is a small example I wrote for Tk. Here, fileevent is Tk's version of IO::Select

#!/usr/bin/perl use warnings; use strict; use Tk; use IPC::Open3; require Tk::ROText; $|=1; my $mw = new MainWindow; my $entry=$mw->Entry(-width => 80)->pack; $mw->Button(-text => 'Execute', -command => \&send_to_shell)->pack; my $textwin =$mw->Scrolled('ROText', -width => 80, -bg =>'white', -height => 24, )->pack; $textwin->tagConfigure( 'err', -foreground => 'red' ); my $pid = open3( \*IN, \*OUT, \*ERR, '/bin/bash' ) or warn "$!\n"; $mw->fileevent( \*OUT, readable => \&read_stdout ); $mw->fileevent( \*ERR, readable => \&read_stderr ); MainLoop; sub read_stdout { if( sysread( OUT, my $buffer, 1024 ) > 0 ){ $textwin->insert( 'end', $buffer ); $textwin->see('end'); } } sub read_stderr { if( sysread(ERR, my $buffer, 1024 ) > 0 ){ $textwin->insert( 'end', $buffer, 'err' ); $textwin->see('end'); } } sub send_to_shell { my $cmd= $entry->get(); print IN "$cmd\n"; }

I'm not really a human, but I play one on earth. Cogito ergo sum a bum

In reply to Re^3: how to get rid of pressing control+c keys by zentara
in thread how to get rid of pressing control+c keys by harsha.reddy

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.