Date: Thu, 28 Nov 2002 07:38:38 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp-workers AT delorie DOT com
Subject: Re: Grep 2.5.1 bug
In-Reply-To: <1038385704.25980.6.camel@leeloo>
Message-ID: <Pine.SUN.3.91.1021128073648.22888A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 27 Nov 2002, Tim Van Holder wrote:

> > DJGPP_204 C:\dj204\tmp>grep -r "ddd" C:\dj204\tmp\*
> > grep: C:\dj204\tmp\RHaaaaaa: Permission denied (EACCES)
> > grep: C:\dj204\tmp\RHbaaaaa: Permission denied (EACCES)
> > grep: C:\dj204\tmp\cvs: Permission denied (EACCES)
> 
> Sounds like directories (especially the 'cvs' one), which suggests that
> grep is reading directories (which is the default, though perhaps it
> shouldn't be on DOSish systems).

In previous versions of Grep, not reading directories was indeed the 
default for DJGPP.  Pewrhaps someone should send patches to the Grep 
maintainer.

> > DJGPP_204 C:\dj204\tmp>grep "ddd" ...\*
> 
> Is .../blah* supposed to ever match directories?

Yes, it matches all files and directories, recursively.