I meant $proc.stdout.lines of course.
On 2017-08-27 07:32:35, alex.jakime...@gmail.com wrote:
> See https://github.com/perl6/doc/issues/1472
>
> Turns out that $proc.lines does the wrong thing, which is probably a
> bug. We do
> need nl-in for Proc::Async, and this nl-in should also be the same
See https://github.com/perl6/doc/issues/1472
Turns out that $proc.lines does the wrong thing, which is probably a bug. We do
need nl-in for Proc::Async, and this nl-in should also be the same as in
IO::Handle.
On 2017-08-18 08:54:36, alex.jakime...@gmail.com wrote:
> Another way to do it is to
Another way to do it is to support custom nl (similarly to how we do
｢$*IN.nl-in = 0.chr｣ now). Split may be an overkill.
On 2017-08-18 08:40:32, c...@zoffix.com wrote:
> On Fri, 18 Aug 2017 08:35:18 -0700, alex.jakime...@gmail.com wrote:
> > Most command line tools support zero-separated input
On Fri, 18 Aug 2017 08:35:18 -0700, alex.jakime...@gmail.com wrote:
> Most command line tools support zero-separated input and output (grep
> -z, find -print0, perl -0, sort -z, xargs -0, sed -z).
>
> And while you can use .stdout.lines to work on things line-by-line,
> doing the same thing with
On Fri, 18 Aug 2017 08:35:18 -0700, alex.jakime...@gmail.com wrote:
> Most command line tools support zero-separated input and output (grep
> -z, find -print0, perl -0, sort -z, xargs -0, sed -z).
>
> And while you can use .stdout.lines to work on things line-by-line,
> doing the same thing with
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131923]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131923 >
Most command line tools support zero-separated input and output
