Mon Apr 7 12:09:00 GMT 1997
On NT, what Jim says is correct. The 'multi-dot' paths being discussed
are probably a special bonus feature (ahem) of the DOS and Windows 95
In a Windows 95 command.com box, a reference to a directory name
consisting of n dots means the n-1st parent directory. Thus
is equivalent to
It is interesting that this notation works with non-command.com exes as
well, so it may be that the Win95 implementation of Win32 generally
> -----Original Message-----
> From: Jim Balter [SMTP:email@example.com]
> Sent: Friday, April 04, 1997 7:10 PM
> To: firstname.lastname@example.org
> Cc: email@example.com; firstname.lastname@example.org
> Subject: Re: Buglist
> email@example.com wrote:
> > Hi Tim, you wrote:
> > : . Bash doesn't understand drive letters, multi-dot relative paths
> > : (eg. "cd ..."), or UNC pathnames (eg. //host/resource).
> > What is a multi-dot path, please? I never saw ... only know . and ..
> > Under Unix ... has no reserved meaning, and AFAIK neither under NT.
> Under win32, paths consisting of only dots, with the exception of .
> and .., are illegal. This is along with a number of other
> illegal characters and combinations, including such winners as
> mkdir -p "abcde/xyz/con/ffo/bar" hanging as it tries to do I/O to the
> "con" device; lots of fun when you untar a 500Meg tar tape from
> some other system that was designed on less ad hoc principles.
> <J Q B>
> For help on using this list, send a message to
> "firstname.lastname@example.org" with one line of text: "help".
For help on using this list, send a message to
"email@example.com" with one line of text: "help".
More information about the Cygwin