[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #18554] feat req: -exec cmd {} more args +

From: Egmont Koblinger
Subject: [bug #18554] feat req: -exec cmd {} more args +
Date: Wed, 20 Dec 2006 17:58:20 +0000
User-agent: Opera/9.01 (X11; Linux i686; U; en)

Follow-up Comment #5, bug #18554 (project findutils):

I'm just reading the standard you have linked, and I still can't see it
explicitely stating that "{}" must _immediately_ precede the "+" sign.

However, it says: "An argument containing only the two characters "{}" shall
be replaced by the set of aggregated pathnames [...]" -- I'd definitely used
other wording if only the last argument could have contained "{}". The
current wording "_An_ argument" gives me a strong feeling that this can be
any argument.

Later it says: "If more than one argument containing only the two characters
"{}" is present, the behavior is unspecified." -- Yet again, this sentence
wouldn't make sense if "{}" was allowed only at one particular place, right
before the "+". IMHO this sentence also implies that "{}" can reside

I agree that having _more_ "{}" arguments before the "+" is a brain-damaged
case and I don't really care how this is handled. I'm only taking about
exactly one "{}" somewhere (anywhere) before the "+".

For rsync, you're right, I didn't know about its --from* options. But for scp
there is no such option, so it's not really straightforward to do something
equivavelent to
find startpoint -tests ... -exec scp {} remote:/dest +
Sure there are possible workarounds involving tricky options of xargs, or
using an scp-wrapper script; but why make things so complicated if they could
have been done much simpler?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]