Re: GNU Parallel Bug Reports --joblog parsing fails for commands containing line feeds.

[Coby Viner]

Hello Ole,

I appreciate your looking into this.

That command sequence works for me as well, including with the previous version (20170522). It is not, however, equivalent to my case, since when composed in the shell in that manner, the job log stores a command delimited by NULL characters and not by line feeds. It appears to be line feeds themselves which cause the problem, as demonstrated by my previously enclosed log files.

I agree that using functions would be better in general. I do, however, still think that it would be nice if GNU Parallel could parse log files with line feeds in the job log. Ignoring lines not starting with a sequence number at least strikes me as a useful feature.

Thanks for your consideration,

Coby

On Fri, June 23, 2017 1:02 pm, Ole Tange wrote:
> On Sat, Jun 17, 2017 at 12:00 AM, Coby Viner <address@hidden>
> wrote:
>
>> --joblog parsing fails for commands containing line feeds.
>
> This works for me:
>
> parallel --jl /tmp/myjl 'echo "command
> with
> newlines"' ::: a b c
>
> parallel --resume --jl /tmp/myjl 'echo "command
> with
> newlines"' ::: a b c d e
>
> $ parallel --version
> GNU parallel 20170622
> Copyright (C) 2007,2008,2009,2010,2011,2012,2013,2014,2015,2016,2017
> Ole Tange and Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> GNU parallel comes with no warranty.
>
> Web site: http://www.gnu.org/software/parallel
>
> When using programs that use GNU Parallel to process data for publication
> please cite as described in 'parallel --citation'.
>
>> Description:
>>
>> I am running GNU Parallel from a bash script in which it is convenient
>> for
>> me to use commands that span over multiple lines (of which the above is
>> a
>> simple contrived example). It would be nice if --joblog parsing were
>> able to
>> ignore lines not starting with a sequence number.
>
> Consider using bash functions instead.
> https://www.gnu.org/software/parallel/man.html#EXAMPLE:-Calling-Bash-functions
>
>
> /Ole
>