This is the mail archive of the
mailing list for the Cygwin project.
Re: Setup 126.96.36.199, Package 'grep' 2.5-1, missing 'egrep.exe' and 'fgrep.exe'
- From: "Max Bowsher" <maxb at ukf dot net>
- To: "Elfyn McBratney" <elfyn-cygwin at exposure dot org dot uk>,"cygwin" <cygwin at cygwin dot com>,"G. Ken Holman" <gkholman at CraneSoftwrights dot com>
- Date: Sun, 2 Feb 2003 21:12:58 -0000
- Subject: Re: Setup 188.8.131.52, Package 'grep' 2.5-1, missing 'egrep.exe' and 'fgrep.exe'
- References: <184.108.40.206.0.20030202154555.02e2eed8@junk> <008701c2cafe$7ccc4160$c2e686d9@webdev>
Elfyn McBratney wrote:
>> Perhaps ... but I'm not running under bash and never have. Did I
>> miss a documented restriction that the programs *only* run under
> It depends on the package. With something like grep you cannot (?)
> call a egrep from cmd.exe/command.com per se as it is a symbolic link
> to grep.exe (a windows shortcut) but you could call it from bash
Ah, but since it is created by setup, it is a system-cookie type symlink,
not a windows-shortcut type symlink.
>> bash -c /bin/egrep
> within your batch scripts.
What about grep -E ? (Which is preferred anyway for maximum portability.)
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html