www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/12/22/09:21:29

From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: LFN listings
Date: 22 Dec 2000 14:14:47 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 25
Message-ID: <91vnkn$6o1$1@nets3.rz.RWTH-Aachen.DE>
References: <91u31i$i72 AT atlas DOT lcc DOT net>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 977494487 6913 137.226.32.75 (22 Dec 2000 14:14:47 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 22 Dec 2000 14:14:47 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

mike friedrichs <mike_fr1 AT txucom DOT net> wrote:
> will there be a day when only the long file name is listed by itself without
> the dos 8.3 format, when using the 'dir' command.

Well, 'dir' is a builtin command of DOS's command.com. User your own judgement
to see how probable it might be that this ever gets changed.

But then, I think 'dir' may have a command line option to suppress the
short names. If so, you can put that into DIROPT and live happily ever
after.

> 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, and
there's absolutely nothing to be done about that, really.  Some way,
blanks separating command line arguments *have* to be distinguished
from blanks inside a filename arguments. Quoting is the usual
technique.




-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019