On Mon, 18 Oct 1999, Tetsuro Teddy FURUYA wrote:
> From: Jacques Vidrine <[EMAIL PROTECTED]>
> Subject: Re: Search a symbol in the source tree
> Date: Sun, 17 Oct 1999 11:37:11 -0500
> n> On 18 October 1999 at 0:39, Tetsuro Teddy FURUYA
>(=?iso-2022-jp?B?GyRCOEVDKxsoQiAbJEJFL086GyhC?=) <[EMAIL PROTECTED]> wrote:
> n> > It seems queer to me that there has been none who has refered to
> n> > find - exec
> n> > pairs.
> n> >
> n> > You may type into shell like;
> n> > $find . -name "*.c" -print -exec "egrep" "-i" "idt" {} \; | less
> n> > Here , "idt" is a search string.
> n>
> n> That's because no one wants a separate invocation of egrep for
> n> every file!
> ^^^^^^
> Probably, except me !
>
> But, what various and interesting methods to search symbols there are !
>
> If we do not restrict the usage of search method, there might be
> yet another methods.
I frequently use find - grep when looking at a novel source tree. The one
problem with the solution given is that if you are looking for a few
instances in hundreds of files, the hits can scroll off the screen and get
lost in the noise. My prefered approach is:
find . -name "*.[c]" -exec grep string {} /dev/null \;
(the /dev/null forces grep to print the filename where a match is found,
and I am an old fogey, learned grep before [ef]grep too lazy to learn
better, should probably use fgrep)
What I'd really like to see is a free implementation of cscope.
Brian Beattie | The only problem with
[EMAIL PROTECTED] | winning the rat race ...
www.aracnet.com/~beattie | in the end you're still a rat
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
