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 To: cygwin AT cygwin DOT com From: "Andrew DeFaria" Subject: Re: grep problems Date: Mon, 14 Jun 2004 09:25:12 -0700 Lines: 23 Message-ID: References: <20040614084213 DOT GA2640 AT efn DOT org> X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: 12.9.207.201 X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 "Yitzchak Scott-Thoennes" wrote in message news:20040614084213 DOT GA2640 AT efn DOT org... > On Mon, Jun 14, 2004 at 10:29:13AM +0200, J?rg Schaible wrote: > > > I have upgraded to latest release of Cygwin and this has not > > > changed things. I have tried the above on a Windows 98 and > > > Windows XP system as well - same results. > > > > > > Any ideas how I get around this problem ? > > > > Learn the syntax. Backslashes have to be escaped by a backslash > > ;-) > > Looks like a cmd.exe shell to me, so no they don't. Well cmd.exe may not consume backslashes as indications of escaping the next character, I would think that grep would. > Also looks like > a non-cygwin grep; at least I can't get grep to say "GREP:". That may be. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/