Re: commented quotes in subshells cause syntax errors
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 long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
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 been fixed for the next version. when you say "next version" you mean like bash-3.2 right ? -mike ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
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, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
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 typing the example code into a terminal: bash-3.1 $ foo=$(#" > ) bash: bad substitution: no closing `)' in $(#" ) bash-3.0 $ foo=$(#" > ) > > bash-3.0: unexpected EOF while looking for matching `"' bash-3.0: syntax error: unexpected end of file notice how bash-3.0 keeps wanting more input until i hit ctrl+d ... almost there ! :) -mike ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
