Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <40504D87.553AF4FD@dessent.net> Date: Thu, 11 Mar 2004 03:29:11 -0800 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: grep bork References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.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/