X-Spam-Check-By: sourceware.org Message-ID: <45894FF0.1020800@yandex.ru> Date: Wed, 20 Dec 2006 10:00:00 -0500 From: Boris Toloknov User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Eric Blake CC: cygwin@cygwin.com Subject: Re: Bash regular expressions References: <45884F6E.5070701@yandex.ru> <4588BC85.2090902@byu.net> In-Reply-To: <4588BC85.2090902@byu.net> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 I tried: [[ abc =~ a.*c ]] && echo It works It doesn't work too. I did't try bash from gnu.org yet but debian bash (version 3.1.0(1)) works with and without quotes. Boris Eric Blake wrote: > According to Boris Toloknov on 12/19/2006 1:45 PM: > >> It seems that regular expressions [[ str =~ regex ]] do not work in bash. >> For example the following expression doesn't match: >> [[ abc =~ 'a.*c' ]] && echo It works >> > > In bash 3.2, the [[ ]] quoting rules changed slightly. Since [[ already > introduces special quoting rules, single quotes are not required; the > regex is already protected by the shell from globbing. Try this instead: > > [[ abc =~ a.*c ]] && echo It works > > And since none of this is cygwin specific, you should report this upstream > to bug-bash AT gnu DOT org if you think it is a bug. > -- 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/