Sender: bcurrie AT tssc DOT co DOT nz
Message-ID: <348D942B.2422@tssc.co.nz>
Date: Wed, 10 Dec 1997 07:55:39 +1300
From: Bill Currie <bcurrie AT tssc DOT co DOT nz>
Organization: Telecommunication Systems Support Centre
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp-workers AT delorie DOT com
Subject: Re: Possible enhancements on v2.02
References: <Pine DOT SUN DOT 3 DOT 91 DOT 971209130538 DOT 7213A-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Eli Zaretskii wrote:
> No, it happens almost always: if DJGPP.ENV says LFN=n and the environment
> doesn't override that, the startup code globs the command line as if LFN
> were set to y, and then resets it to LFN=n when it loads DJGPP.ENV.

Isn't that a bug? If LFN=n then the program should never see long file
names.  It seems you're saying that no matter what LFN is set to, you
will always get the long fine names on the command line.  This seems
very wrong to me.

Bill
-- 
Leave others their otherness