Problems with ash-20040127-3 (Attn: bash maintainer)
Lev Bishop
lev.bishop@gmail.com
Sun Jul 10 15:18:00 GMT 2005
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/
More information about the Cygwin
mailing list