Hi,
Sorry for not noticing this earlier but bash-3.2 bash has introduced a minor
regression in my build environment (i686-pc-linux-gnu):
warning: some of these tests will fail if you do not have UTF-8
warning: locales installed on your system.
warning: please ignore any differences consisting on
Hi
ncurses-5.5 fails to build with bash-3.2 installed as sh. Here's the
distilled testcase:
cat > testcase << "EOF"
TABSIZE=`grep -v '^[ #]' $CAPS | grep -v "^$" | grep -v "^capalias"| grep -v
"^infoalias" | wc -l`
EOF
$ bash -n testcase
testcase: line 1: unexpected EOF while looking for match
On Wed, Aug 30, 2006 at 01:01:06AM -0400, Paul Jarc wrote:
> Greg Schafer <[EMAIL PROTECTED]> wrote:
> > Thanks for trying to clarify it for me. Let me put it another way: If I
> > change Line 1 above to an if/then style statement instead of "&&" ie:
On Wed, Aug 30, 2006 at 04:28:35AM +, Eric Blake wrote:
> > > > #!/bin/sh
> > > > set -e
> > > >
> > > > func () {
> > > > false && echo false
> > > > true && echo true
> > > > false && echo false
> ^^^ Line 1
>
> > > > }
> > > >
> > > > func
> ^^^ Line 2
>
> > > >
> > > > echo done
> >
On Wed, Aug 30, 2006 at 12:03:51AM -0400, Paul Jarc wrote:
> Greg Schafer <[EMAIL PROTECTED]> wrote:
> > #!/bin/sh
> > set -e
> >
> > func () {
> > false && echo false
> > true && echo true
> > false && echo f
Hi
Here's a test case which demonstrates the problem:
#!/bin/sh
set -e
func () {
false && echo false
true && echo true
false && echo false
}
func
echo done
It never echoes "done" because func() returns 1. This seems to go against
what the bash manual says about "set -e"
"Exit immedia
Hi
This issue was reported earlier but with apparently no response:
http://lists.gnu.org/archive/html/bug-bash/2006-05/msg00018.html
When su'd to a non-root user under Linux the configure check fails:
checking whether /dev/fd is available... absent
Here is a suggested patch as per the foll
Chet Ramey wrote:
> There is a difference in behavior between bash-3.0 and bash-3.1 involving
> parsing of single- and double-quoted strings occurring in old-style
> command substitution. The difference has to do with how backslashes are
> processed. This patch restores a measure of backwards
Chet Ramey wrote:
> There is a difference in behavior between bash-3.0 and bash-3.1 involving
> parsing of single- and double-quoted strings occurring in old-style
> command substitution. The difference has to do with how backslashes are
> processed. This patch restores a measure of backwards co
