Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: Mysterious gdb behavior. From: Robert Collins To: derbyshire@globalserve.net Cc: cygwin@cygwin.com In-Reply-To: <3D4454AD.5172.56808E0A@localhost> References: <3D439956.10056.53A4C2DE@localhost> <3D4454AD.5172.56808E0A@localhost> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-QxKE3gvDhor1U9PwK7tM" Date: 29 Jul 2002 10:43:37 +1000 Message-Id: <1027903418.7873.12.camel@lifelesswks> Mime-Version: 1.0 --=-QxKE3gvDhor1U9PwK7tM Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2002-07-29 at 10:31, Paul Derbyshire wrote: > On 28 Jul 2002 at 21:20, Robert Collins wrote: > > 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 > But once it's set, it's set.=20 Untrue. Edit /etc/passwd. > > 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. >=20 > Why isn't most of it (the open source stuff, that is) already=20 > patched?=20 Good question. > > *Please*, research before asserting. Because non-cygwin1.dll linked > > programs don't unquote arguments this solution actually sucks worse tha= n > > the current status quo. >=20 > Obviously it should quote them only to other Cygwin linked programs.=20 > Which it can identify by whether it launching something in the cygwin=20 > tree or not. Untrue. cygcheck, wish and other programs in the cygwin tree may be native programs, and cygwin linked programs may reside outside the tree. > In fact, the general rule to quote arguments to a=20 > program launched purely by name and not to one launched by an=20 > absolute path would probably work pretty well. Everything on Cygwin's=20 > PATH can be assumed to unquote arguments I'd imagine. Imagine away... Cygwin's path includes the windows directory - and that means many programs that won't unquote arguments. =20 > > Those short names do not always exist - you'll need a fallback for thos= e > > cases. >=20 > They do. Windows always assigns an 8.3 version of a filename that has=20 > a long name, a long extension, multiple extensions (foo.tar.gz,=20 > etc.), or an unusual character in the name such as a space. How to Disable Automatic Short File Name Generation: I'm bowing out of this thread. You've shown yourself incapable of discriminating between your imagination and reality. It makes it very hard to discuss the topic at hand.=20 =20 As a final comment in the vague hope you'll try rather than just arguing from imagination: * You should try Chris's list of tests. * You could ask the list (via the archives or direct) the simplest way to get rid of the space in your cygwin home directory.=20 Rob --=-QxKE3gvDhor1U9PwK7tM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEABECAAYFAj1Ej7kACgkQI5+kQ8LJcoJyawCfS3N/sEhvHHNzilzGm1Qf1uOR FB0AoK8r6MZyAlfa6omWWRaORMaxeO9T =QG4y -----END PGP SIGNATURE----- --=-QxKE3gvDhor1U9PwK7tM--