Re: commented quotes in subshells cause syntax errors

2006-04-15 Thread Chet Ramey
Mike Frysinger wrote: > On Friday 14 April 2006 22:52, Chet Ramey wrote: >>> >>> foo=$( #' >>> echo hi) >> This has already been fixed for the next version. > > when you say "next version" you mean like bash-3.2 right ? Yeah, I mean like bash-3.2. :-) Chet -- ``The lyf so short, the craft so

Re: commented quotes in subshells cause syntax errors

2006-04-14 Thread Mike Frysinger
On Friday 14 April 2006 22:52, Chet Ramey wrote: > Mike Frysinger wrote: > > not a regression as bash-2.05 / bash-3.0 also barf on this ... i imagine > > someone has already filed this, but i couldnt seem to find it in the > > mailing lists ... > > > > foo=$( #' > > echo hi) > > This has already be

Re: commented quotes in subshells cause syntax errors

2006-04-14 Thread Chet Ramey
Mike Frysinger wrote: > not a regression as bash-2.05 / bash-3.0 also barf on this ... i imagine > someone has already filed this, but i couldnt seem to find it in the mailing > lists ... > > foo=$( #' > echo hi) This has already been fixed for the next version. Chet -- ``The lyf so short, th

commented quotes in subshells cause syntax errors

2006-04-14 Thread Mike Frysinger
not a regression as bash-2.05 / bash-3.0 also barf on this ... i imagine someone has already filed this, but i couldnt seem to find it in the mailing lists ... foo=$( #' echo hi) now the neat thing is that with bash-3.1 (unlike older versions), the open/close parens are detected properly when