delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=0.1 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <34270643.post@talk.nabble.com> |
Date: | Wed, 8 Aug 2012 02:11:06 -0700 (PDT) |
From: | AngusC <anguscomber AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: problem using recursive grep (-r option) |
In-Reply-To: | <CAM7SfR2UneeDR+Np59MAhR8opFzcEUVceYKe0xxLi=-8riw53g@mail.gmail.com> |
MIME-Version: | 1.0 |
References: | <34266659 DOT post AT talk DOT nabble DOT com> <CAM7SfR2UneeDR+Np59MAhR8opFzcEUVceYKe0xxLi=-8riw53g AT mail DOT gmail DOT com> |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
I did try the --include way but in Cygwin it didn't work for some reason. Neither does find "." -name "*.log" -exec grep -nH "my pattern" {} \; or find "." -name "*.log" | grep -nH "my pattern" So struggling about on Cygwin at the moment. Sean Daley-2 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 > > > -- View this message in context: http://old.nabble.com/problem-using-recursive-grep-%28-r-option%29-tp34266659p34270643.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |