Re: commented quotes in subshells cause syntax errors

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

BUG and Suggestion in bash(1) MAN page

Dear All, =Environment= GNU bash, version 3.00.16(1)-release (i686-pc-linux-gnu) Copyright (C) 2004 Free Software Foundation, Inc. Linux 2.6.15.1 #2 PREEMPT i686 Intel(R) Pentium(R) III Mobile CPU 1133MHz GenuineIntel GNU/Linux on IBM T23 laptop. =Environment===

Re: commented quotes in subshells cause syntax errors

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

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