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 i9J5TUh5017010 for ; Tue, 19 Oct 2004 05:29:30 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id CC8E076F5F for ; Tue, 19 Oct 2004 05:29:29 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJmgC-0000an-82 for migo@homemail.com; Tue, 19 Oct 2004 01:37:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CJmfq-0000aU-Fs for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 01:36:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CJmfp-0000aA-RC for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 01:36:42 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJmfp-0000a0-P1 for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 01:36:41 -0400 Received: from [144.140.70.20] (helo=gizmo10bw.bigpond.com) by monty-python.gnu.org with smtp (Exim 4.34) id 1CJmYT-0005U9-R8 for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 01:29:06 -0400 Received: (qmail 16496 invoked from network); 19 Oct 2004 05:29:02 -0000 Received: from unknown (HELO bwmam11.bigpond.com) (144.135.24.100) by gizmo10bw.bigpond.com with SMTP; 19 Oct 2004 05:29:02 -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/148737992) with SMTP id 148737992; Tue, 19 Oct 2004 15:29:02 +1000 Received: by freedbms.net (Postfix, from userid 1000) id 93EE13C078; Tue, 19 Oct 2004 15:29:31 +1000 Subject: Re: [Gnu-arch-users] Re: File naming conventions From: Zenaan Harkness To: John Meinel In-Reply-To: <4174A530.7090507@johnmeinel.com> 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> <41745D7F.5000102@johnmeinel.com> <417499B9.2040301@johnmeinel.com> <1098163105.19575.128.camel@whiskas.cashpoolcomps.com> <4174A530.7090507@johnmeinel.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1098163771.19575.138.camel@whiskas.cashpoolcomps.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 19 Oct 2004 15:29:31 +1000 Cc: arch 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: 1012 Lines: 37 On Tue, 2004-10-19 at 15:25, John Meinel wrote: > Zenaan Harkness wrote: > >>Actually, I really wish grep had the workaround, because otherwise I > >>have to do this little hack: > >> > >>grep -rn "what I want" * | grep -v "{arch}/" > >> > >>which means it still has to grep all of those files, it just doesn't > >>tell me about it. > > > > > > So reverse your greps. > > > > That doesn't actually work. Because the final grep is actually greping > out the filename given by the first grep, not the text in the file. > Something that might work is: > > $ find . ! -path "*arch*" -print0 | xargs -0 -n50 grep -rn "what I want" find . | grep -v *arch* | xargs grep -n "blah" ?doesn't that do basically what you want? (don't know how the -print0 fits into that one though) cheers zen _______________________________________________ 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/