Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <00c701c2caff$dcd08700$78d96f83@pomello> From: "Max Bowsher" To: "Elfyn McBratney" , "cygwin" , "G. Ken Holman" References: <5 DOT 2 DOT 0 DOT 9 DOT 0 DOT 20030202154555 DOT 02e2eed8 AT junk> <008701c2cafe$7ccc4160$c2e686d9 AT webdev> Subject: Re: Setup 2.249.2.5, Package 'grep' 2.5-1, missing 'egrep.exe' and 'fgrep.exe' Date: Sun, 2 Feb 2003 21:12:58 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 >> bash? > > 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.) Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/