Re: Incompatibility between bash versions running a configure script

[EMAIL PROTECTED] wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i486 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' > -DCONF_VENDOR='pc' -DLOCA

Incompatibility between bash versions running a configure script

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

printf builtin doesn't handle stdout errors correctly

Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux Compiler: gcc -I/usr/src/packages/BUILD/bash-2.05b -L/usr/src/packages/BUILD/bash-2.05b/../readline-4.3 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' -DCONF_OSTYPE='linux' -DCONF_MACHTYPE='i

Re: terminating lines with accidental eof

[EMAIL PROTECTED] (Martin Wheatley) wrote: > (ie commands are only executed when the user hits enter and NOT > executed when an I/O error occurs on the input stream). EOF is not an error. If there is an error, then certainly bash should not execute an partial command it has buffered, but that won

Re: terminating lines with accidental eof

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Martin Wheatley on 7/5/2006 2:58 AM: > > Linking /bin/sh to /bin/bash does NOT maintain the bourne shell API. > > For example, > > Tradition using a traditional bourne shell ... > > xn-sysadm-4 $ sh > xn-sysadm-4 $ PWD=fred > xn-sysadm

Re: terminating lines with accidental eof

Bob Proulx wrote: Please keep your replies to the mailing list to keep everyone involved in the discussion instead of singling out one individual. Also the mailing list is archived and others may search the archive to find previous discussions. Martin Wheatley wrote: The following can be us

Re: terminating lines with accidental eof

Bob Proulx wrote: Martin Wheatley wrote: You also asked ... Is there an example of another command shell which handles this situation in a different and possibly better way? /bin/sh handles the situation correctly (in our opinion) On my system /bin/sh is a symlink to /bin/bash and beh

Re: terminating lines with accidental eof

Andreas Schwab wrote: > Bob Proulx writes: > > A small point. You are aware that the tty driver converts enter from > > the keyboard into a newline? See the tty driver 'icrnl' flag setting. > > Programs never read a carriage return. Programs actually read a > > newline character. > > Only in ic

Re: terminating lines with accidental eof

[EMAIL PROTECTED] (Bob Proulx) writes: > A small point. You are aware that the tty driver converts enter from > the keyboard into a newline? See the tty driver 'icrnl' flag setting. > Programs never read a carriage return. Programs actually read a > newline character. Only in icanon mode, othe