From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22541 invoked from network); 6 Sep 2005 13:59:01 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 6 Sep 2005 13:59:01 -0000 Received: (qmail 28333 invoked from network); 6 Sep 2005 13:58:54 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 6 Sep 2005 13:58:54 -0000 Received: (qmail 22358 invoked by alias); 6 Sep 2005 13:58:46 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9393 Received: (qmail 22348 invoked from network); 6 Sep 2005 13:58:45 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 6 Sep 2005 13:58:45 -0000 Received: (qmail 27263 invoked from network); 6 Sep 2005 13:58:45 -0000 Received: from vms044pub.verizon.net (206.46.252.44) by a.mx.sunsite.dk with SMTP; 6 Sep 2005 13:58:40 -0000 Received: from candle.brasslantern.com ([71.116.79.190]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IME00N73ETQ22C7@vms044.mailsrvcs.net> for zsh-users@sunsite.dk; Tue, 06 Sep 2005 08:58:40 -0500 (CDT) Received: from candle.brasslantern.com (IDENT:schaefer@localhost [127.0.0.1]) by candle.brasslantern.com (8.12.11/8.12.11) with ESMTP id j86DwcnU009757 for ; Tue, 06 Sep 2005 06:58:38 -0700 Received: (from schaefer@localhost) by candle.brasslantern.com (8.12.11/8.12.11/Submit) id j86DwbMF009756 for zsh-users@sunsite.dk; Tue, 06 Sep 2005 06:58:38 -0700 Date: Tue, 06 Sep 2005 13:58:37 +0000 From: Bart Schaefer Subject: Re: Problem with glob qualifier e In-reply-to: <200509060651.36809.arvidjaar@newmail.ru> To: zsh-users@sunsite.dk Message-id: <1050906135837.ZM9755@candle.brasslantern.com> MIME-version: 1.0 X-Mailer: Z-Mail (5.0.0 30July97) Content-type: text/plain; charset=us-ascii References: <87u0gza316.fsf@trews52.bothi.fi> <200509052123.08360.arvidjaar@newmail.ru> <1050905190530.ZM30762@candle.brasslantern.com> <200509060651.36809.arvidjaar@newmail.ru> Comments: In reply to Andrey Borzenkov "Re: Problem with glob qualifier e" (Sep 6, 6:51am) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 On Sep 6, 6:51am, Andrey Borzenkov wrote: } Subject: Re: Problem with glob qualifier e } } } On Monday 05 September 2005 23:05, Bart Schaefer wrote: } > } } > } (I do not know why xargs here won't process arguments seperated by } > } spaces, it should) } > } > I'm not sure what you mean? xargs never processes arguments separated } > by spaces. It always wants newlines or NULs. } } then manual page is wrong: Ah, hmm, yes, you're right, and I've misremembered. What I was thinking of is how xargs normally batches up its arguments. One of the oft-stated reasons for using find . -whatever ... | xargs something rather than find . -whatever ... -exec something {} \; is that the latter runs something once for every file, whereas the former runs it fewer times on groups of files. However, my statement was correct for the case of `xargs -i' because the manual page goes on to say: --replace[=replace-str], -i[replace-str] Replace occurences of replace-str in the initial arguments with names read from standard input. Also, unquoted blanks do not terminate arguments. If replace-str is omitted, it defaults to "{}" (like for `find -exec'). Implies -x and -l 1.