This is the mail archive of the
mailing list for the Cygwin project.
Re: Setup 220.127.116.11, Package 'grep' 2.5-1, missing 'egrep.exe' and 'fgrep.exe'
- From: Christopher Faylor <cgf-cygwin at cygwin dot com>
- To: "G. Ken Holman" <gkholman at CraneSoftwrights dot com>
- Cc: cygwin at cygwin dot com
- Date: Sun, 2 Feb 2003 15:25:12 -0500
- Subject: Re: Setup 18.104.22.168, Package 'grep' 2.5-1, missing 'egrep.exe' and 'fgrep.exe'
- References: <22.214.171.124.0.20030202145134.00b7f880@junk>
- Reply-to: cygwin at cygwin dot com
On Sun, Feb 02, 2003 at 03:05:07PM -0500, G. Ken Holman wrote:
>I used to use one of the Cygwin B packages where the egrep.exe utility was
>I'm on an XP system and I downloaded replacement packages yesterday and
>ensured that I included the "grep" package.
>I went to use "egrep.exe" and found it wasn't installed. I did find an
>egrep.1 but it just points to grep.
egrep and fgrep are symbolic links to grep.exe. Both work properly when
invoked from bash. I just checked.
>p.s. http://cygwin.com/bugs.html points to http://cygwin.com/lists.html and
>says where *not* to send bugs, but not where bugs should be sent for
>problems like this ... I would have thought that would be a FAQ: "which
>bugs (by example) go to which mail lists?"
The cygwin mailing list says that it is for "just about all things
cygwin" with "two exceptions".
Is grep, egrep, or fgrep listed as one of the two exceptions?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html