Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: Date: Sun, 10 Jul 2005 11:18:38 -0400 From: Lev Bishop Reply-To: Lev Bishop To: cygwin AT cygwin DOT com Subject: Re: Problems with ash-20040127-3 (Attn: bash maintainer) In-Reply-To: <070820052135.10000.42CEF188000C8AFE0000271022064246130A050E040D0C079D0A@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <070820052135 DOT 10000 DOT 42CEF188000C8AFE0000271022064246130A050E040D0C079D0A AT comcast DOT net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j6AFImoo011605 On 08/07/05, Eric Blake wrote: > Meanwhile, you will have to wait patiently until the upstream > maintainer releases a patch (because I haven't the faintest clue > where in the lexer to look for fixing his parse error). Repeated > pinging on the cygwin list will not help speed up the situation. In bash 2.05b, file parse.y, line 2179ish: else if MBTEST(was_dollar && (ch == '(' || ch == '{' || ch == '[')) /* ) } ] */ /* check for $(), $[], or ${} inside quoted string. */ Maybe something like: else if MBTEST(open=='"' && was_dollar && (ch == '(' || ch == '{' || ch == '[')) /* ) } ] */ /* check for $(), $[], or ${} inside " quoted string. */ Might do the trick? I haven't tried it. Would need testing from someone who understands POSIX quoting in detail, to ensure it doesn't break other convoluted quoting rules... -- 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/