Re: bash 2.04.11(1)-release weirdness if no #! line
From:
Lack Mr G M
Subject:
Re: bash 2.04.11(1)-release weirdness if no #! line
Date:
Wed, 28 Mar 2001 13:39:07 BST
In article <200103281216.f2SCGMF25826@skeeve.com>, arnold@skeeve.com (Aharon
Robbins) writes:
|>
|> This explains why ksh93 changed so that only interactive
|> shells run the $ENV file. Have you considered doing this
|> for bash?
I hope not! I've got enough problems with getting non-interactive
shells to set up *login* environments already. The correct place for
this fix is where you have put it - in the script itself.
Why should interactive and non-interactive scripts *ever* be treated
differently?
--
--------- Gordon Lack --------------- gml4410@ggr.co.uk ------------
This message *may* reflect my personal opinion. It is *not* intended
to reflect those of my employer, or anyone else.