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 i9J1OKOl019262 for ; Tue, 19 Oct 2004 01:24:21 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id 8984976F12 for ; Tue, 19 Oct 2004 01:24:22 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJiqx-0006TF-V1 for migo@homemail.com; Mon, 18 Oct 2004 21:31:56 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CJiqa-0006RE-2j for gnu-arch-users@gnu.org; Mon, 18 Oct 2004 21:31:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CJiqY-0006QQ-M5 for gnu-arch-users@gnu.org; Mon, 18 Oct 2004 21:31:30 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJiqY-0006Q8-Ep for gnu-arch-users@gnu.org; Mon, 18 Oct 2004 21:31:30 -0400 Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CJiie-00010k-Q7; Mon, 18 Oct 2004 21:23:20 -0400 Received: from [66.149.231.226] (helo=purple.west.spy.net) by mx20.gnu.org with esmtp (Exim 4.34) id 1CJiZ2-00058a-0p; Mon, 18 Oct 2004 21:13:24 -0400 Received: from [10.9.254.245] (sjc-dist3-e3.2wire.com [63.203.253.2]) by purple.west.spy.net (Postfix) with ESMTP id B7931217; Mon, 18 Oct 2004 18:12:54 -0700 (PDT) In-Reply-To: <20041019004004.GC3264@fencepost> References: <1098074588.29545.40.camel@whiskas.cashpoolcomps.com> <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> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0316CE40-216C-11D9-A63A-000393CFE6B8@spy.net> Content-Transfer-Encoding: 7bit From: Dustin Sallings Subject: Re: [Gnu-arch-users] Re: File naming conventions Date: Mon, 18 Oct 2004 18:12:57 -0700 To: Miles Bader X-Mailer: Apple Mail (2.619) Cc: arch , Zenaan Harkness , John Meinel 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: 820 Lines: 32 On Oct 18, 2004, at 17:40, Miles Bader wrote: > 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). DESCRIPTION The xargs utility reads space, tab, newline and end-of-file delimited arguments from the standard input and executes the specified utility with them as arguments. -- Dustin Sallings _______________________________________________ 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/