Received: from spf5.us4.outblaze.com (spf5.us4.outblaze.com [205.158.62.27]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id i9J43c8s023765 for ; Tue, 19 Oct 2004 04:03:38 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id A680277105 for ; Tue, 19 Oct 2004 04:03:25 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJlKt-0006Em-KS for migo@homemail.com; Tue, 19 Oct 2004 00:10:59 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CJlKW-0006Eh-Pw for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:10:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CJlKW-0006EU-6r for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:10:36 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJlKW-0006ER-41 for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:10:36 -0400 Received: from [144.140.70.40] (helo=gizmo05bw.bigpond.com) by monty-python.gnu.org with smtp (Exim 4.34) id 1CJlCZ-000436-Mz for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:02:24 -0400 Received: (qmail 27986 invoked from network); 19 Oct 2004 04:02:21 -0000 Received: from unknown (HELO bwmam11.bigpond.com) (144.135.24.100) by gizmo05bw.bigpond.com with SMTP; 19 Oct 2004 04:02:21 -0000 Received: from cpe-144-132-220-21.nsw.bigpond.net.au ([144.132.220.21]) by bwmam11.bigpond.com(MAM REL_3_4_2a 180/148632971) with SMTP id 148632971; Tue, 19 Oct 2004 14:02:22 +1000 Received: by freedbms.net (Postfix, from userid 1000) id 104543C078; Tue, 19 Oct 2004 14:02:52 +1000 Subject: Re: [Gnu-arch-users] Re: File naming conventions From: Zenaan Harkness To: arch In-Reply-To: <20041019004910.GD3264@fencepost> References: <1098092294.5219.8.camel@johannes> <20041018181822.GD9196@puritan.pcp.ath.cx> <8D7869BC-213A-11D9-A63A-000393CFE6B8@spy.net> <1098141434.19575.42.camel@whiskas.cashpoolcomps.com> <20041018233511.GA31642@fencepost> <0D336108-2162-11D9-A63A-000393CFE6B8@spy.net> <20041019002621.GA3264@fencepost> <41745FDF.2000907@johnmeinel.com> <20041019004004.GC3264@fencepost> <20041019004910.GD3264@fencepost> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1098158570.19575.90.camel@whiskas.cashpoolcomps.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 19 Oct 2004 14:02:50 +1000 X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 1292 Lines: 31 On Tue, 2004-10-19 at 10:49, Miles Bader wrote: > On Mon, Oct 18, 2004 at 08:40:04PM -0400, Miles Bader wrote: > > > Isn't this only true if you used the -0 flag? > > > > No. Think about it -- why would xargs have problems with whitespace? It > > uses newline-separated records as its input (so other whitespace is fine), > > and it uses execv or whatever to invoke its command (Which Uses An Argv > > Interface For Arguments, And So Has No Problems With Whitespace, Or Newlines > > For That Matter). > > Er, cancel that -- as Dustin points out in a later message, I was wrong: > xargs seems to treats any whitespace as a separator, not just newlines. > > I'm truly shocked actually; it's a completely stupid things for xargs to do. > Maybe xargs originally came from system-v instead of bell-labs... :-/ > > Now excuse me while I wipe this egg off my face... We can thank Daniel Bernstein (djbdns etc) for introducing these options to both find and xargs. It is in fact a surprisingly recent development ... Windows<->Unix convergence thing (SAMBA servers I guess). _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/