X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B0C4C2A.3080502@gmail.com> Date: Tue, 24 Nov 2009 21:12:10 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin bash regexp matching doesn't treat "\b" properly References: <26500158 DOT post AT talk DOT nabble DOT com> <26500814 DOT post AT talk DOT nabble DOT com> In-Reply-To: <26500814.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com aputerguy wrote: > OK - I think I found the answer which is that \b is a GNU extension not > recognized in cygwin. > > So, I guess the question now is there an alternative way of recognizing word > boundaries? Bash man page for '~=' refers to man regex(3) which refers to man regex(7) which describes word boundary markers as below: $ [[ "foo" =~ [[:\<:]]foo[[:\>:]] ]]; echo $? 0 $ [[ "foobar" =~ [[:\<:]]foo[[:\>:]] ]]; echo $? 1 $ (Note that I had to backslash-escape the < and > there. In other contexts that might not be needed.) cheers, DaveK -- 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