comment on

Did I miss something really obvious?

Well...

The following code shows a successful 'cd' for me

#! /usr/bin/perl
use strict;
use IPC::Run qw( start pump finish );

my ($input, $output, $errput);
$input="";
$output="";
my $subp = start([ '/bin/bash' ],
                       \$input,
                       \$output,
                       \$errput) or die $@;

print $errput;
$input .= "cd /work/drjohnson\n";
pump $subp until length $input == 0;
$input .= "pwd\n";
pump $subp until $output =~ /\n/;
print "$output\n";
$subp->finish;
[download]

If you have a runnable example of where it doesn't work for you, I'd be glad to try it. You might also try IPCRUNDEBUG. Do an 'export IPCRUNDEBUG=details' before running your script. I believe what the author meant was that you couldn't do things like 'cd' (well, chdir) in your parent script between pump calls.

fnord

In reply to Re: Automating a shell session: cd does not work by Illuminatus
in thread Automating a shell session: cd does not work by pokki

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks