Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: Re: Mysterious gdb behavior.
From: Robert Collins <rbcollins AT cygwin DOT com>
To: derbyshire AT globalserve DOT net
Cc: cygwin AT cygwin DOT com
In-Reply-To: <3D439956.10056.53A4C2DE@localhost>
References: <3D43020A DOT 30440 DOT 5155C2C9 AT localhost> 
	<3D439956 DOT 10056 DOT 53A4C2DE AT localhost>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-xzi8QGm5dd/zXcEozZ7R"
Date: 28 Jul 2002 21:20:53 +1000
Message-Id: <1027855254.5866.32.camel@lifelesswks>
Mime-Version: 1.0

--=-xzi8QGm5dd/zXcEozZ7R
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2002-07-28 at 21:12, Paul Derbyshire wrote:
> OK. Is anyone going to actually suggest a solution here? And don't=20
> say "rename the directory", I don't imagine renaming the home=20
> directory to something other than your user name is going to do=20
> anything but cause more trouble.

I won't say what you don't want to hear. You might consider searching
the friendly archives, because they *tell* you what is worse - a home
dir with spaces or a home dir w/o spaces.
=20
> Really, spaces in path names shouldn't bother any part of the system.=20

should !=3D doesn't. I agree, it sucks. Still, unless you want to patch
all the broken software out there (which BTW includes pure win32
programs last time I checked), then you need to deal with it one way or
another.

> Wherever path names with spaces are handed off to shells or whatever=20
> they should be quoted, that's all.=20

*Please*, research before asserting. Because non-cygwin1.dll linked
programs don't unquote arguments this solution actually sucks worse than
the current status quo.

> If path names that went into=20
> scripts, parameter lists, or whatever were defensively quoted there=20
> would never be an issue.

Untrue, as indicated above.

> If it really can't be made to work, then=20
> perhaps the system should automatically use the short version of=20
> names with spaces in them?=20

Those short names do not always exist - you'll need a fallback for those
cases. It's an interesting idea though, perhaps you'd like to contribute
a patch. I'd be happy to give you pointers on what do look at to create
such a patch.

Rob


--=-xzi8QGm5dd/zXcEozZ7R
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEABECAAYFAj1D05UACgkQI5+kQ8LJcoLD9QCfUmNjQiGUrvlE9L7ztt9TD/ej
hioAn3ndS/jpTEL5o3CE/lXSa9KGq3Wl
=+Q0/
-----END PGP SIGNATURE-----

--=-xzi8QGm5dd/zXcEozZ7R--