[ On Tuesday, October 1, 2002 at 17:20:00 (+0000), Joerg Klemenz wrote: ]
> Subject: Re: CVS commit: basesrc/bin/ksh
>
> But ksh will also execute ENV for
> non interactive shells if you call a script from a login shell if I'm
> not mistaken. I would consider that an incarnation of the exact same
> "design flaw".

If $ENV is set when the shell starts then it will do what it is
documented to do.  This is exactly what's best, no more and no less.

> What [c|k]sh really needs, imho, is a third startup file that "frees"
> the existing two ones for interactive use *only*.

This is trivially arranged with proper run-time checks in $ENV, as I and
others have already shown.

-- 
								Greg A. Woods

+1 416 218-0098;            <g.a.woods@ieee.org>;           <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>