Received: from spf3.us4.outblaze.com (spf3.us4.outblaze.com [205.158.62.25]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id i9J4R6cF029765 for ; Tue, 19 Oct 2004 04:27:07 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf3.us4.outblaze.com (Postfix) with ESMTP id 116F1539DF for ; Tue, 19 Oct 2004 04:27:05 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJlhi-0004KK-8C for migo@homemail.com; Tue, 19 Oct 2004 00:34:34 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CJlhP-0004KD-Gp for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:34:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CJlhP-0004K1-2v for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:34:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CJlhO-0004Jy-Vn for gnu-arch-users@gnu.org; Tue, 19 Oct 2004 00:34:15 -0400 Received: from [66.149.231.226] (helo=purple.west.spy.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CJlZa-0006SM-3J; Tue, 19 Oct 2004 00:26:11 -0400 Received: from [192.168.1.50] (dustinti.west.spy.net [192.168.1.50]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client did not present a certificate) by purple.west.spy.net (Postfix) with ESMTP id 62BC256D; Mon, 18 Oct 2004 21:24:56 -0700 (PDT) In-Reply-To: <41745D7F.5000102@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> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Dustin Sallings Subject: Re: [Gnu-arch-users] Re: File naming conventions Date: Mon, 18 Oct 2004 21:24:55 -0700 To: John Meinel X-Mailer: Apple Mail (2.619) Cc: arch , Zenaan Harkness , Miles Bader 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: 3496 Lines: 86 On Oct 18, 2004, at 17:19, John Meinel wrote: > How do you handle this for CVS? Or is it just that ctags knows about > CVS directories and ignores them? Well, the easy answer is that I don't use CVS for anything anymore. :) But when I did, there was rarely anything in a CVS directory that was of interest to ctags or grep or anything else I used. But I always thought it was pretty annoying there, too. It makes no sense for the to have used a CVS status directory that was so intrusive. > I was thinking about what was said that find * -name ... | xargs gets > replaced by tla inventory. > > But find * also has problems with CVS/SVN, etc. In fact, if you run it > in any directory below you will still go into hidden directories. I've not used subversion, and really have no interest in it. I used CVS for a long time, but it was a pain. Things are getting better, and whenever I can think of a way to make things ever-so-slightly better, I'll bring it up. > I always work around it with: > > find . ! -path "*{arch}*" -name .... | xargs That does seem to help some, but it's just another workaround. > But I also tend to work in trees with many nested projects, so I don't > have just one top-level directory. > > Heck I just looked in the man page and I think: > > ctags -R . --exclude="*{arch}*" > actually this also works, but if you have a strange hierarchy it might > fail: > > ctags -R . --exclude="*arch*" > > This one does have the advantage of ignoring .arch-inventory and > .arch-ids as well, though probably ctags wouldn't understand those > files and ignores them anyway. This is another workaround with a different syntax. Perhaps I should've used gnu grep as an example instead, since (at least in my manpage), there is no --exclude functionality. I'm not convinced that having the --exclude functionality in every application would even be all that desirable, but having to use it all the time seems like it would. > Now that all that is said, I personally don't care whether it is > .arch, or {arch}. I know when I first started I thought .arch would > have been better. But now, I don't really care. I think {arch} stands > out nicely when browsing. In Windows the .files aren't hidden anyway > so there isn't much of a benefit there. I think a lot of people have got themselves used to the idea that the {arch} directory will be there and accept it. Some say they even like it. I'm really not that interested in the browsing aspect, though. If I want to know that a directory is arch managed just by looking at it, then I can add my own flag there...one more informative for my needs (i.e. arch-dustin@spy.net--c--b--v or something). > I *really* like the ",blah" to mean this is a temporary file, and have > started using it very frequently. I never use the + or =, though. I'm > not really sure what is what (I think + is precious, ie not source, > but I'm at a loss for =) I'm right with you on this one. -- SPY My girlfriend asked me which one I like better. pub 1024/3CAE01D5 1994/11/03 Dustin Sallings | Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE L_______________________ I hope the answer won't upset her. ____________ _______________________________________________ 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/