RE: bug in fgrep from http://unxutils.sourceforge.net/

[Jack Thompson]

Thanks for your quick reply.  My ESP is quite limited, so I better just
paste my command ...

fgrep -r "def" *.py

Python is new to me, but, the string 'def' appears in about a dozen
python scripts that I've written over the past month.  The files are in
several directories all under a directory called symBuild, one of the
subs is Utils.  

So, I exectute that command in symBuild, and get a list of all the files
and locations in symBuild, but not the ones under Utils.  I cd to Utils
and repeat the command and get all the hits for the Utils directory.
The command seems to work find, but why aren't the Utils files listed in
the call under symBuild?

When I work on UNIX systems, I usually just use find and pipe the files
through grep - maybe I'm not using fgrep right????

Thanks for your help,
-Jmt



-----Original Message-----
From: Bob Proulx [mailto:address@hidden 
Sent: Wednesday, August 24, 2005 8:56 AM
To: Jack Thompson
Cc: address@hidden
Subject: Re: bug in fgrep from http://unxutils.sourceforge.net/

Jack Thompson wrote:
>             It seems like win2k really doesn't want users to be able
to
> effectively search for strings within files in sub directories.
They've
> taken some very important features of their developer studio away too
-
> probably because they don't want developers to be able to work
> efficiently without relying on their framework.

Uhm...  I have no idea what you are talking about here.  Is this
related to a question about something related to GNU project software?

> So, I tried using your fgrep, but that seems not to work correctly
> in this environment - I cannot get it to recurse sub directories.
> Am I missing something?  Is there an update?

GNU grep does recurse fine down directories.

I am rubbing my temples and visualizing very hard but I cannot see
what you have typed at the keyboard.  Perhaps your ESP quotient is too
low for thought transfer like this.  Or you may not be thinking about
this problem right now and that is why we can't read your mind on this
matter.

First, check the actual version of grep that you are using.  GNU grep
will display this with the --version option.  We always talk about
grep because grep implements fgrep and egrep, and fgrep and egrep have
been deprecated in favor of the -F and -E options.

  grep --version

On my system that says this:

  grep (GNU grep) 2.5.1

Then show us the commands that you used.  Such as this command to grep
recursively down a directory tree.

  grep -r MANPATH= .

Bob