[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] Re: File naming conventions
From: |
John Meinel |
Subject: |
Re: [Gnu-arch-users] Re: File naming conventions |
Date: |
Mon, 18 Oct 2004 19:19:11 -0500 |
User-agent: |
Mozilla Thunderbird 0.8 (Windows/20040913) |
Dustin Sallings wrote:
On Oct 18, 2004, at 16:35, Miles Bader wrote:
[...]
In fact, my complaint seems to be the opposite of what you're'
saying. I have no problem typing {arch}, I have a problem avoiding it.
For example, where I would before type the following:
ctags -R *
I now get to type something like this:
ctags `tla inventory -s`
Except...oops:
desktop:~/prog/p4gw/cms 3011> ctags `tla inventory -s`
/usr/local/bin/ctags: Argument list too long.
[...]
How do you handle this for CVS? Or is it just that ctags knows about CVS
directories and ignores them?
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 always work around it with:
find . ! -path "*{arch}*" -name .... | xargs
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.
I think most tools that you want to use already will have ways of
avoiding directories (SVN and CVS put one in *every* directory, so you
can't just get away with avoiding them in this directory.)
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 *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 =)
John
=:->
signature.asc
Description: OpenPGP digital signature
- [Gnu-arch-users] Re: File naming conventions, (continued)
- [Gnu-arch-users] Re: File naming conventions, Miles Bader, 2004/10/18
- Re: [Gnu-arch-users] File naming conventions, Johannes Berg, 2004/10/18
- Re: [Gnu-arch-users] File naming conventions, Dustin Sallings, 2004/10/18
- [Gnu-arch-users] Re: File naming conventions, Nikolai Weibull, 2004/10/18
- Re: [Gnu-arch-users] Re: File naming conventions, Dustin Sallings, 2004/10/18
- Re: [Gnu-arch-users] Re: File naming conventions, Zenaan Harkness, 2004/10/18
- Re: [Gnu-arch-users] Re: File naming conventions, Miles Bader, 2004/10/18
- Re: [Gnu-arch-users] Re: File naming conventions, Dustin Sallings, 2004/10/18
- Re: [Gnu-arch-users] Re: File naming conventions,
John Meinel <=
- Re: [Gnu-arch-users] Re: File naming conventions, Miles Bader, 2004/10/18
- Re: [Gnu-arch-users] Re: File naming conventions, Zenaan Harkness, 2004/10/19
- Re: [Gnu-arch-users] Re: File naming conventions, Dustin Sallings, 2004/10/19
- Re: [Gnu-arch-users] Re: File naming conventions, Zenaan Harkness, 2004/10/19
- Re: [Gnu-arch-users] Re: File naming conventions, John Meinel, 2004/10/19
- Re: [Gnu-arch-users] Re: File naming conventions, Zenaan Harkness, 2004/10/19
- Re: [Gnu-arch-users] Re: File naming conventions, John Meinel, 2004/10/19
- Re: [Gnu-arch-users] Re: File naming conventions, Zenaan Harkness, 2004/10/19
- Re: [Gnu-arch-users] Re: File naming conventions, Miles Bader, 2004/10/18
- Re: [Gnu-arch-users] Re: File naming conventions, John Meinel, 2004/10/18