Date: Thu, 28 Nov 1996 08:43:20 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Chris Waters <design AT netcom DOT com>
Cc: djgpp AT delorie DOT com
Subject: Re: Changing directories in BASH
In-Reply-To: <designE1Jp8o.F3D@netcom.com>
Message-Id: <Pine.SUN.3.91.961128083723.8104H-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Wed, 27 Nov 1996, Chris Waters wrote:

> >Since Unix generally doesn't support such directory names, I'd guess 
> >`bash' fails to support them too.
> 
> WHY DO PEOPLE KEEP SAYING THIS??  Unix supports file/directory names
> with spaces JUST FINE!  Posting statements about OSes you aren't
> familiar with on the net is not a good idea!

I *am* familiar with Unix, I just failed to say *exactly* what I meant, 
which is unfortunate, but hardly a crime.

Let me rephrase: many Unix programs generally don't support filenames and
directories with embedded blanks.  Unix certainly doesn't *encourage* use
of blanks in pathnames (I have never seen such filenames on Unix boxes). 
The backslash escaping might not always work in DJGPP ports, because DJGPP
tries very hard to support both forward- and backslashes in pathnames. 

> Bash may also be confused by the "c:" which, since it doesn't start with
> a slash, may cause bash to think it has a relative pathname.

No, the port supports drive letters, so this shouldn't be a problem.