Re: Quoting error: unexpected EOF while looking for matching `''

[Ole Tange]

On Wed, Sep 22, 2010 at 10:50 AM, Hans Schou <address@hidden> wrote:

> address@hidden:~/parallel$ ls NEWS | ./src/parallel grep "'"
> sh: -c: line 0: unexpected EOF while looking for matching `''
> sh: -c: line 1: syntax error: unexpected end of file
> address@hidden:~/parallel$ ls NEWS | ./src/parallel -q grep "'"
> * Alias for DBURL can contain '?query' part with %-quoting.
>   sem 'sleep 2; echo foo'; sem 'sleep 1; echo bar'; sem --wait
>   sem -j2 'sleep 2; echo foo'; sem -j2 'sleep 1; echo bar'; sem --wait
>   cat tab_sep_table | parallel --colsep '\t' echo col1 {1} col2 {2}
> * --sshloginfile '..' means use ~/.parallel/sshloginfile
>
> address@hidden:~/tmp/parallel$ ls NEWS | ./src/parallel grep "'"
> sh: -c: line 0: unexpected EOF while looking for matching `''
> sh: -c: line 1: syntax error: unexpected end of file
> address@hidden:~/tmp/parallel$ ls NEWS | ./src/parallel -q grep "'"
> * Alias for DBURL can contain '?query' part with %-quoting.
>   sem 'sleep 2; echo foo'; sem 'sleep 1; echo bar'; sem --wait
>   sem -j2 'sleep 2; echo foo'; sem -j2 'sleep 1; echo bar'; sem --wait
>   cat tab_sep_table | parallel --colsep '\t' echo col1 {1} col2 {2}
> * --sshloginfile '..' means use ~/.parallel/sshloginfile
>
> address@hidden ~/tmp/parallel $ ls NEWS | ./src/parallel grep "'"
> sh: -c: line 0: unexpected EOF while looking for matching `''
> sh: -c: line 1: syntax error: unexpected end of file
> address@hidden ~/tmp/parallel $ ls NEWS | ./src/parallel -q grep "'"
> * Alias for DBURL can contain '?query' part with %-quoting.
>   sem 'sleep 2; echo foo'; sem 'sleep 1; echo bar'; sem --wait
>   sem -j2 'sleep 2; echo foo'; sem -j2 'sleep 1; echo bar'; sem --wait
>   cat tab_sep_table | parallel --colsep '\t' echo col1 {1} col2 {2}
> * --sshloginfile '..' means use ~/.parallel/sshloginfile

All of these do what is expected. None of them show the problem described in:

http://lists.gnu.org/archive/html/bug-parallel/2010-09/msg00005.html

Can you re-test on the computer that the original problem existed on?


/Ole