Subject: Re: CVS commit: basesrc/bin/ksh
To: Joerg Klemenz <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 10/01/2002 14:23:53
[ 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; <firstname.lastname@example.org>; <email@example.com>
Planix, Inc. <firstname.lastname@example.org>; VE3TCP; Secrets of the Weird <email@example.com>