Date: Tue, 13 Apr 1999 10:01:27 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Kbwms AT aol DOT com
cc: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>,
        djgpp-workers AT delorie DOT com
Subject: Re: LBInstDJ
In-Reply-To: <ab9210eb.2443acf8@aol.com>
Message-ID: <Pine.SUN.3.91.990413100103.29746I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 12 Apr 1999 Kbwms AT aol DOT com wrote:

> I find it a chilling prospect that we would propose making automatic
> changes to autoexec.bat.  I, for one, have two safeguards:
> 
>     1) My autoexec.bat is a read-only file (as is config.sys).
> 
>        What is planned in this case?

What *should* be planned?  The installer could do anything, provided
that we agree it's a good idea.  In particular, if you copy the
original and edit the copy, the OS removes the protection by default,
unless the installer is careful to copy the protection as well.

>     2) The lion's share of my work is done in a shell like Bash called
>        KornShell.  The proposed changes will never be seen.

Why not?  If the environment variables are set before the shell is
launched, doesn't the shell inherit all of them, including PATH and
DJGPP?