Path: utzoo!utgpu!watmath!att!dptg!rutgers!gatech!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.questions
Subject: Re: ENV file in ksh: is this smart? legal?
Keywords: ksh, ENV
Message-ID: <10890@smoke.BRL.MIL>
Date: 31 Aug 89 01:18:32 GMT
References: <716@rodan.acs.syr.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <716@rodan.acs.syr.edu> jdpeek@rodan.acs.syr.edu (Jerry Peek) writes:
>#2.  The next problem I have with ENV files -- if their name is stored
>in the environment (export ENV) -- is that Korn shell script files
>(shell programs) read them too.  I have some stuff in my ENV file that
>screws up shell scripts.

That's a Korn shell design botch.  Apparently DGK thought that the C shell
behavior should be mimicked.  Too bad he didn't first notice what a pain
it already was for C shell users.  When Doug Kingston and I added a
similar feature to the BRL Bourne shell, we were more careful, and I think
ours works right.  It does NOT get sourced for shell scripts (unless they
decide to source the file themselves, which would be exceedingly rare).