public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: bug with grep 3.0.2 in cygwin 3.0.7
Date: Wed, 28 Aug 2019 12:51:00 -0000	[thread overview]
Message-ID: <ce0890bd-f1b1-5a77-4999-9793d9a0df25@cs.umass.edu> (raw)
In-Reply-To: <1207614124.1217647925.1566976580120.JavaMail.root@zimbra76-e14.priv.proxad.net>

On 8/28/2019 3:16 AM, akiki@free.fr wrote:
> 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
> 
> 
> I have to backslash ^ to be OK like : grep -E 'a\^b'
> 
> 
> Is-it a bug ?
> I don't know if all versions of cygwin and grep are concerned.

 From my reading of the man page, it's either a program bug or a
documentation bug.  It could well be the latter since -E extended
regular expressions require a number of other metacharacters to
be backslash quoted.  However, the documentation does not mention
the ^ metacharacter.

Regards - EM

--
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

  reply	other threads:[~2019-08-28 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1910922536.1217465852.1566975322390.JavaMail.root@zimbra76-e14.priv.proxad.net>
2019-08-28  8:32 ` akiki
2019-08-28 12:51   ` Eliot Moss [this message]
2019-08-28 13:33   ` Eric Blake
2019-08-29 19:20   ` Andrey Repin
2019-08-30  6:12     ` Eliot Moss
2019-08-30  7:48       ` Brian Inglis
2019-08-30 15:34         ` Eliot Moss
2019-08-30  7:50       ` Duncan Roe
2019-08-30 13:04         ` Jose Isaias Cabrera
2019-08-30  7:55       ` Andrey Repin
2019-09-23 14:42   ` Chris Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ce0890bd-f1b1-5a77-4999-9793d9a0df25@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).