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 i9J3tP8s019663 for ; Tue, 19 Oct 2004 03:55:25 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id E47C077075 for ; Tue, 19 Oct 2004 03:55:23 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJlD8-000392-4O for migo@homemail.com; Tue, 19 Oct 2004 00:02:58 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CJlCn-00038v-VX for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:02:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CJlCn-00038j-He for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:02:37 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJlCn-00038g-Ek for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:02:37 -0400 Received: from [144.140.71.19] (helo=gizmo09ps.bigpond.com) by monty-python.gnu.org with smtp (Exim 4.34) id 1CJl5I-0003BE-Vy for gnu-arch-users@gnu.org; Mon, 18 Oct 2004 23:54:53 -0400 Received: (qmail 6095 invoked from network); 19 Oct 2004 03:54:51 -0000 Received: from unknown (HELO psmam11.bigpond.com) (144.135.25.100) by gizmo09ps.bigpond.com with SMTP; 19 Oct 2004 03:54:51 -0000 Received: from cpe-144-132-220-21.nsw.bigpond.net.au ([144.132.220.21]) by psmam11.bigpond.com(MAM REL_3_4_2a 225/115906451) with SMTP id 115906451; Tue, 19 Oct 2004 13:54:51 +1000 Received: by freedbms.net (Postfix, from userid 1000) id 44CE93C078; Tue, 19 Oct 2004 13:55:21 +1000 Subject: Re: [Gnu-arch-users] Re: File naming conventions From: Zenaan Harkness To: arch In-Reply-To: <20041019002621.GA3264@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> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1098158119.19575.83.camel@whiskas.cashpoolcomps.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 19 Oct 2004 13:55:19 +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: 1242 Lines: 31 On Tue, 2004-10-19 at 10:26, Miles Bader wrote: > On Mon, Oct 18, 2004 at 05:01:39PM -0700, Dustin Sallings wrote: > > desktop:~/prog/p4gw/cms 3011> ctags `tla inventory -s` > > /usr/local/bin/ctags: Argument list too long. > > > > I suppose since this version of ctags has an option to avoid > > clobbering the tags file on a second invocation, I can use > > xargs...unless there's whitespace or something in a filename somewhere. > > Slightly off-topic, but xargs doesn't have any problem with typical > whitespace in file names; the main issue is _newlines_ in filenames. Not quite the point. xargs doesn't, but when space-containing filenames are passed by xargs to just about any other Unix tool, that tool interprets the spaces to mean filename endings. Thus the point of persuading find and xargs to use \0 as argument/filename endings. If you try it (or have been bitten by it, like me) you will discover that find and xargs don't work as expected (in most scenarios) without the -print0 and -0 options... _______________________________________________ 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/