From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 34384 invoked by alias); 30 Aug 2019 07:48:07 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 34358 invoked by uid 89); 30 Aug 2019 07:48:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=BAYES_50,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=H*F:D*com.au, D*free.fr!, D*free.fr, 3.0.2 X-HELO: mail104.syd.optusnet.com.au Received: from mail104.syd.optusnet.com.au (HELO mail104.syd.optusnet.com.au) (211.29.132.246) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 Aug 2019 07:48:01 +0000 Received: from dimstar.local.net (unknown [49.176.30.160]) by mail104.syd.optusnet.com.au (Postfix) with SMTP id 3E8C243ECD2 for ; Fri, 30 Aug 2019 17:47:58 +1000 (AEST) Received: (qmail 8682 invoked by uid 501); 30 Aug 2019 07:47:56 -0000 Date: Fri, 30 Aug 2019 07:50:00 -0000 From: Duncan Roe To: cygwin@cygwin.com Subject: Re: bug with grep 3.0.2 in cygwin 3.0.7 Message-ID: <20190830074756.GB25467@dimstar.local.net> Mail-Followup-To: cygwin@cygwin.com References: <1910922536.1217465852.1566975322390.JavaMail.root@zimbra76-e14.priv.proxad.net> <1207614124.1217647925.1566976580120.JavaMail.root@zimbra76-e14.priv.proxad.net> <8910174142.20190829220811@yandex.ru> <806ab587-a07c-1616-1486-ebb258ace1d9@cs.umass.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <806ab587-a07c-1616-1486-ebb258ace1d9@cs.umass.edu> User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-08/txt/msg00413.txt.bz2 On Thu, Aug 29, 2019 at 09:42:46PM -0400, Eliot Moss wrote: > On 8/29/2019 3:08 PM, Andrey Repin wrote: > > Greetings, akiki@free.fr! > > > > > Hi, > > > I encounter some problem with grep option -E on cygwin 3.0.7 > > > > > > > echo "a^b" | grep "a^b" #answer a^b ie it's OK > > > but > > > echo "a^b" | grep -E "a^b" #answer nothing " for me it's KO > > > > That's an expected result of an impossible constraint. > > > > > I have to backslash ^ to be OK like : grep -E 'a\^b' > > > > Yes. > > > > > Is-it a bug ? > > > > No. > > > > > I don't know if all versions of cygwin and grep are concerned. > > > > RTFM, this is regexp basics. > > There was a really great answer to this earlier. I tried an > answer, but was wrong. One has to read the "fine print" really > carefully. At first I thought it was a bug, at least in the > documentation, but the meaning of a^b, when ^ is the metacharacter, > is kind of subtle (IMO at least). It's easy to miss that > subtlety and think that if ^ is not at the beginning of an > expression it will be treated as an ordinary character ... > > But my main point is that RTM would be enough; RTFM seemed > to me perhaps a little more rude than necessary. > > Regards - EM > I don't see anything to object to in "Read The Fine Manual" ;) Cheers ... Duncan. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple