Dear all,
GNU parallel 20190222 apparently does not resume from a job log if you
add "--null" or "--delimiter foo" to its command line arguments. Is
this the intended behavior or a bug?
The following shell transcript shows what I am describing. "^C"
indicates where parallel is killed through Ctrl + c.
------
$ cd /tmp && mkdir parallel-test && cd parallel-test
$ for i in $(seq 1 100); do touch test$i; done
$ find . -name 'test*' | parallel --resume --joblog log echo {}
.
./test1
./test2
^C
$ find . -name 'test*' | parallel --resume --joblog log echo {}
./test3
./test4
./test5
[...]
./test100
$ find . -name 'test*' | parallel --resume --joblog log echo {}
[nothing]
------
As you can see, the job is resumed. Now let's try "--null".
------
$ rm log
$ find . -name 'test*' -print0 | parallel --null --resume --joblog log
echo {}
.
./test1
./test2
^C
$ find . -name 'test*' -print0 | parallel --null --resume --joblog log
echo {}
.
./test1
./test2
[...]
./test100
$ find . -name 'test*' -print0 | parallel --null --resume --joblog log
echo {}
.
./test1
./test2
[...]
./test100
------
Sincerely,
D. Bohdan
