Re: problem using recursive grep (-r option)

[ping <songpingemail at gmail dot com>]

On 8/7/2012 1:55 PM, Sean Daley wrote:
> On Tue, Aug 7, 2012 at 11:08 AM, AngusC <> wrote:
> > If I use the command:
> >
> > grep -nH -r "my pattern" *.*
> >
> > I get results back as expected
> >
> > But if the file pattern is like this:
> >
> > grep -nH -r "my pattern" *.log
> >
> > I get no results back (Even though I have a ton of files with this pattern
> > with .log file extension).
> >
> > Am I doing something wrong?
> > --
> The first one works because *.* will match everything your current directory,
> including sub-directories and it will recurse through each of them.  The
> second example will first match anything in your current directory with a .log
> extension and try to grep it (if it's a file) or recurse through it if
> it's a directory.
>
> What I believe you want to do (at least works on Linux) is
> grep -nH -r "my pattern" --include "*.log" .
>
> Sean
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
I think this is the best answer ever so far.

also it looks for me:
 grep -nHr "pattern" *.*
   equals:
 grep -nHr "pattern" .

I use the latter alot to quickly locate a file per content.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple