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
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
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= =BUG Executing: man bash and in the INVOCATION section, it reads: " When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. " While this is true for interactive login shells, it's not for non-interactive login shells. Executing: bash -l -c echo $- will not source ~/.bash_logout ==BUG ===Suggested Solution Change it to: " When an interactive login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. " ===Suggested Solution ===Other Suggestions In INVOCATION section, after: " A login shell is one whose first character of argument zero is a -, or one started with the --login option. " It's really confusing unless you already know about this (then the purpose of this is? :p ). Can we add an example for added clarity, such as: " A login shell is one whose first character of argument zero is a -, or one started with the --login option. E.g., logging in to a system will provide a shell with `echo $0` = '-bash' if executed immediately after login, which is a login shell. Xterm login shells are not login shells. " Another suggestions goes into the same section (INVOCATION): Can we explain a little about what a non-interactive, non-login shell will do, regarding startup files, etc.? Thank you for your consideration. ===Other Suggestions BTW, the people at irc://irc.freenode.net #bash really helped! Please join us there! Regards, Q.D. ___ 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
