Re: No Gnus feature request: simpler file structure for synching

["Steven E. Harris" <seh@panix.com>]

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> The »*~« part is not properly quoted (o=opening, c=closing quotes).

Yes, I had noticed that while fiddling around with the exclude
settings, which rsync was ignoring. I tried various quoting schemes,
including this odd one, and it finally seemed to work, so I left
it. The real problem had been the omission of the '=' character
between "--exclude" and "*~" tokens.

> You may use one of the following:
> |     "                                   '*~'"
> |     '                                   "*~"'
> |     '                                   \'*~\''

While these all look good, and I tried them all again in good faith,
it turns out none of these three alternatives work properly on my
system (Cygwin, Windows 2000). This one works like the first I posted
(second-level quotes removed):

cmd='rsync -e ssh -lptD -vuzb --exclude=*~'


>> REMOTE=Panix:~/temp/sync/gnus
>
> Some Unix-Standard (SUS2, SYS3?  I don't remember exactly) suggest to
> use lower case variables. [1]

I was just copying some other shell script idioms I've seen. The
uppercase names help make the variable names stand out. Enclosing them
in braces helps too. The argument you offer makes sense, though, so
I'll change the case.

>>     $CMD -r $* $REMOTE/home/ .
>               ^^ better use "$@" (including the quotes)

Why is one preferable to the other in this case? I read the Bash man
page on $* and $@ and can't really see how one should choose.

-- 
Steven E. Harris