Re: bash 2.04.11(1)-release weirdness if no #! line

[Aharon Robbins]

Thanks Chet, this does seem to be the issue, in that when I
edited my $ENV to have

        [ -t 0 ] && stty erase '^h'

it stopped complaining. Aha! I just realized why it wasn't
complaining when I invoked it with arguments; then stdin is
still hooked to my xterm.

This explains why ksh93 changed so that only interactive
shells run the $ENV file.  Have you considered doing this
for bash?

In any case, much thanks for the quick response.

Arnold Robbins

Chet said:
> I can't reproduce it with my current version of bash-2.05 on RedHat 6.1,
> nor with bash-2.04.  I'd check to see whether or not your startup files
> are being run, since the error message is coming from `stty'.

Arnold first reported:
> > You don't know how long this took me to track down.
> > 
> > Bash version:
> >     GNU bash, version 2.04.11(1)-release (i386-redhat-linux-gnu)
> >     Copyright 1999 Free Software Foundation, Inc.
> > 
> > System:
> >     Redhat GNU/Linux 7.0.
> > 
> > To reproduce, put the following in a file named foo:
> > 
> >     cat "$@"
> > 
> > Make it executable.  Note that there is no #! line.  Here's what
> > happens:
> > 
> >     Script started on Tue Mar 27 17:28:06 2001
> >     bash2-2.04$ ./foo foo > /dev/null
> >     bash2-2.04$ ./foo < foo > /dev/null
> >     stty: standard input: Inappropriate ioctl for device
> >     bash2-2.04$ exit
> >     
> >     Script done on Tue Mar 27 17:28:19 2001
> > 
> > If I add a #! /bin/sh at the top, I no longer get the error message.