Re: GNU Parallel Bug Reports parallel --pipe no longer honours --max-lines setting

[Ole Tange]

On Tue, Oct 1, 2013 at 1:23 AM, Shawn Halpenny <address@hidden> wrote:
> I recently upgraded from an older version (2012-10-22) of parallel to
> 2013-09-22 and discovered that --max-lines no longer has any effect if
> --pipe is used.

Yes. A bug was fixed in parallel-20130222.

If you read the manual for --max-lines you will see it behaved wrongly
before 20130222:

                When used with --pipe: Read records of max-lines.

It did not read records at the specified number of lines (or rather:
It read a single record and not as many as would fit in a --block).
This is typically used for processing files that have a fixed number
of lines per record (e.g. 4 lines per record), but we do not care how
many records are read.

What you are looking for is -N:

                When used with --pipe -N is the number of records to
read. This is somewhat slower than --block.


/Ole