Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: <40504D87.553AF4FD@dessent.net>
Date: Thu, 11 Mar 2004 03:29:11 -0800
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: grep bork
References: <NUTMEG8Jecd92bXCH5n00000108 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Dave Korn wrote:

> Ok, since when has the plus sign been a bash metachar?  I'm sure I've never
> had to escape it before, but am I remembering wrong?

From the grep manpage:

> In basic regular expressions the metacharacters ?, +, {, |,  (,  and  )
> lose  their  special  meaning; instead use the backslashed versions \?,
> \+, \{, \|, \(, and \).

Since you're calling grep as just "grep" (and not egrep or "grep -E")
you're using basic regexps, not extended.

Brian

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