Date: Sun, 24 Dec 2000 08:12:25 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: LFN listings
In-Reply-To: <91vnkn$6o1$1@nets3.rz.RWTH-Aachen.DE>
Message-ID: <Pine.SUN.3.91.1001224080818.7747D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 22 Dec 2000, Hans-Bernhard Broeker wrote:

> But then, I think 'dir' may have a command line option to suppress the
> short names.

I'm not aware of such an option; if someone knows how to do that, please 
tell.

On NT, unless you say "dir /x", you don't get the short 8+3 aliases.  But 
on Windows 9X, the aliases are always shown in long directory listings, 
and I don't see a way to disable that.

> > and will using LFN's without applying quotes to the LFN be obtained.
> 
> You only ever need quotes around an LFN if it contains blanks

Some other characters, such as `=' and `,', might need quotes as well.  
Using forward slashes in file names is possible, at least in some cases, 
by quoting the entire file name.

Note that the handling of quotes in COMMAND.COM is buggy: you can easily 
crash the DOS box if you forget the closing quote.