rsFalse has asked for the wisdom of the Perl Monks concerning the following question:

Hello,
I'm getting this strange error warning when printing bigger output of 'perlbrew exec perl' into pipe to 'less -S':

$ perlbrew exec perl -wle 'print " A" x 1e3 for 1 .. 1e2' | less -S
Command [perl -wle 'print " A" x 1e3 for 1 .. 1e2'] terminated with ex
+it code 0 ($? = 13) under the following perl environment:

[download]
Any ideas why it occurs?
P.S. I have two perls in perlbrew.

Replies are listed 'Best First'.
Re: perlbrew: Command [ ... ] terminated with exit code 0 ($? = 13)
by haukex (Archbishop) on Mar 15, 2021 at 10:28 UTC

    $? = 13 is (typically) a SIGPIPE. You probably exited less before scrolling through all the output.

[reply]
[d/l]
[select]
      Ye. For sure. Thanks!
      If doesn't throw a warning if I scroll whole output.

      But if I try with slightly changed line: 
      perlbrew exec perl -wle 'print " A" x 1e0 for 1 .. 1e2' | less -S

      [download]
      There is no warning, although I didn't scroll the whole output.
[reply]
[d/l]
        But if I try with slightly changed line: 
        perlbrew exec perl -wle 'print " A" x 1e0 for 1 .. 1e2' | less -S

        [download]
        There is no warning, although I didn't scroll the whole output.

        perl -wle 'print " A" x 1e0 for 1 .. 1e2' is 300 bytes, while perl -wle 'print " A" x 1e3 for 1 .. 1e2' is 200100 bytes. Since you're piping the output of perl to another program, perl's output isn't line-based (see e.g. Suffering from Buffering), and so what I'm fairly certain is happening is that perl is simply outputting the 300 bytes in one go. Update: Because perl -wle '$|++; print " A" x 1e0 for 1 .. 1e2' isn't killed by SIGPIPE either, it may also have something to do with how much data a pipe can buffer, but I'm not an expert on that.

[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom