hello,
> Actually -- looks like it is there :-) though on the
> Proc page, not the 'run' page --
too far from the expected lines. so maybe we should just add a link ?
> I'm curious about whether you could rely
> on a line being emitted right away -- e.g.
> if there is some output-buffering of
On Thursday, June 6, Marc Chantreux wrote:
> this isn't obvious to guess that '-' means "you can connect the
> subprocess directly to the perl interpreter". i really think this
> example is worth to be added in the documentation.
Actually -- looks like it is there :-) though on the
Proc page,
> Something like this?
> my $p = run 'cat', '-n', :in, :out;
> $p.in.say($_) for ;
> $p.in.close;
> say $p.out.slurp;
*that* simple!!! perfect ... thanks a lot!
this isn't obvious to guess that '-' means "you can connect the
subprocess directly to the perl interpreter".
On Thursday, June 6, Marc Chantreux wrote:
> my $p = run 'cat', '-n', in => $*OUT, :out;
> $*OUT.say for < i bet on you, raku >;
> $*ERR.say: $p.out.slurp;
>
> my $p = run 'cat', '-n', in => "/dev/stdout", :out;
> $*OUT.say for < i bet on you, raku >;
> $*ERR.say:
hello people,
French Perl Workshop is coming and would be a better
event if *you* take part of it
https://journeesperl.fr/jp2019/talks
now the problem ...
let's say i have a raku script to wrap mutt.
in this script, i have
* $body is the content of the body my message
* $subject
