On 8/9/2012 2:27 AM, Andrey Repin wrote:
Greetings, AngusC!
This works
find . -name "*.log" | grep -nH -r "my pattern" *.*
What? This is ridiculous.
Do you read what you write?
Indeed. Can we all agree that this thread has drifted far enough away
from anything Cygwin-specific that it c
Greetings, AngusC!
> This works
> find . -name "*.log" | grep -nH -r "my pattern" *.*
What? This is ridiculous.
Do you read what you write?
--
WBR,
Andrey Repin (anrdae...@freemail.ru) 09.08.2012, <10:27>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems
On 2012-08-08, marco atzeri wrote:
> On 8/8/2012 11:11 AM, AngusC wrote:
> >
> DO NOT TOP POST !
>
> >I did try the --include way but in Cygwin it didn't work for some reason.
Both of these work fine for me in Cygwin (on Windows XP):
grep -nH -r "my pattern" --include "*.log" .
grep -nH
On 8/8/2012 11:11 AM, AngusC wrote:
DO NOT TOP POST !
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" {} \;
find "." -name "*.log" -exec grep -nH "my pattern" \{\} \;
--
Problem reports: htt
This works
find . -name "*.log" | grep -nH -r "my pattern" *.*
marco atzeri-4 wrote:
>
> On 8/7/2012 5:08 PM, 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 patt
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
On 7 August 2012 16:57, marco atzeri wrote:
> On 8/7/2012 5:08 PM, 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
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
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
On 8/7/2012 7:15 PM, AngusC wrote:
do not top post
Why would I use find . -name "*.log" -exec grep -nH "my pattern" \{\} \;
which is much longer to type when I can use grep ... -r ???
because it works ?
But if the file pattern is like this:
grep -nH -r "my pattern" *.log
I get no re
Why would I use find . -name "*.log" -exec grep -nH "my pattern" \{\} \;
which is much longer to type when I can use grep ... -r ???
marco atzeri-4 wrote:
>
> On 8/7/2012 5:08 PM, AngusC wrote:
>>
>> If I use the command:
>>
>> grep -nH -r "my pattern" *.*
>>
>> I get results back as expected
On 8/7/2012 5:08 PM, 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
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 s
13 matches
Mail list logo
