Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Dan Haynes" <haynes AT anchorgaming DOT com>
To:	"Jeffrey Juliano" <juliano AT cs DOT unc DOT edu>, <cygwin AT sources DOT redhat DOT com>
Subject:	Spaces in paths (was RE: Newbie: W2K and Mounting problem.)
Date:	Fri, 13 Oct 2000 09:47:20 -0600
Message-ID:	<003901c0352c$dee38620$0600000a@tired>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To:	<764984234.971427593@[192.168.0.16]>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.2106.4

Just a vaguely related comment... an odd thing I happened to find the other
day from a windows shell (cmd.exe). I accidentally discovered that cmd.exe
treats the following identically:

cd \usr      \src
cd \usr\src

I knew that cmd.exe always tried to "imagine" quotes when paths with spaces
were used, but I didn't realize is "patches up" misspelled names like this.

Of course this should have no bearing on how Cygwin defines the behaviour of
spaces and quotes, but I wonder if it cmd.exe that strips the spaces out of
there, or is it the Windows operating system call to change directories? If
it's the latter, how might that affect the Cygwin implementation?

Regards,

  Dan Haynes


> -----Original Message-----
> From: cygwin-owner AT sources DOT redhat DOT com
> [mailto:cygwin-owner AT sources DOT redhat DOT com]On Behalf Of Jeffrey Juliano
> Sent: Friday, October 13, 2000 7:00 AM
> To: cygwin AT sources DOT redhat DOT com
> Subject: Re: Newbie: W2K and Mounting problem.
>
>
>
>
> --On Thurs, Oct 12, 2000 3:51 PM -0400 Chris Faylor wrote:
>
> > Both the archives and the FAQ should state that if you are
> using backslash
> > style paths in a bash shell, you have to either do:
>
> I would expect
>
>    http://sources.redhat.com/cygwin/faq/faq.html#SEC44
>
> to explain it, and failing that, assume it's not mentioned in the FAQ.
>
> I wish people would do an archive search before posting for help.
>  (Is that
> mentioned in the FAQ?)  But in this case, perhaps the error message from
> mount could be improved to make it easier for a newby to figure it out
> himself.
>
> Seems to me (haven't checked the source) that the single
> backslash sucks up
> the space character, leaving the mount command with just a single
> argument.
> If so, then shouldn't mount dump a usage statement instead of giving the
> error that it does?
>
> If I'm right, I'm willing to volunteer for this one, but not until next
> week.
>
> -jeff
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -