Date: Tue, 11 Nov 2008 19:36:22 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: Aggelidis Nikos <aggelidis.news@gmail.com> Subject: Re: Using grep to search a repository Message-ID: <200811111936.23400.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <30fc78250811111017l5f087dc8o52c1f1367e056ecd@mail.gmail.com> References: <30fc78250811111017l5f087dc8o52c1f1367e056ecd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 11 November 2008 19:17:28 Aggelidis Nikos wrote:
> Hi to all the list,
>
> i have a project with a lot of bash scripts in a folder hierarchy.I
> haven't wrote the project myself so many times i have to search for
> the definition of a function. For this purpose i decided to use grep
> {recursively}.
> The problem is that the project is an svn repository... so grep
> returns results from .svn and it is really messes up the outcome of
> grep. I tried bypassing the problem using the `--exclude=file_pattern'
> but since its use is for files not directories it doesn't work.... So
> the questions are:
>
> 1) Can i bypass certain directories{i.e. '.svn' or 'log/'}, using
> grep? {or a combination of tools + grep}
man find(1), specifically -path and -exec arguments. Example:
find . -type f \( \! -path '*/.svn/*' -a \! -path '*/log/*' \) \
-exec grep foo {} +
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811111936.23400.fbsd.questions>