From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22291 invoked by alias); 30 Aug 2019 13:04:47 -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 22277 invoked by uid 89); 30 Aug 2019 13:04:47 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=-0.6 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,SPF_PASS autolearn=no version=3.3.1 spammy=acronyms, decades, carefully.=c2, produced!?= X-HELO: mailsrv.cs.umass.edu Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 Aug 2019 13:04:46 +0000 Received: from [192.168.0.14] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 9CBE24042D6A; Fri, 30 Aug 2019 09:04:44 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: bug with grep 3.0.2 in cygwin 3.0.7 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> <0ca60f0b-4765-b870-7eef-85d9944e0406@SystematicSw.ab.ca> From: Eliot Moss Message-ID: Date: Fri, 30 Aug 2019 15:34:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <0ca60f0b-4765-b870-7eef-85d9944e0406@SystematicSw.ab.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2019-08/txt/msg00424.txt.bz2 On 8/30/2019 2:12 AM, Brian Inglis wrote: > On 2019-08-29 19:42, Eliot Moss wrote: >> On 8/29/2019 3:08 PM, Andrey Repin wrote: >>>> 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. > > https://cygwin.com/acronyms/#RTFM exists and has been amusing rather than rude > in our industry for decades, especially in non-native English locales e.g. here > in this list: "Read The Fine Manual"; but RTM for software products is usually > "Release To Manufacturing", from the days when media was produced! Ok, I relent! E -- 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