Message-ID: <4B5FD16E.4060107@monai.ca>
Date: Tue, 26 Jan 2010 21:38:54 -0800
From: Steven Monai <steve+cygwin AT monai DOT ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bug: cygport fails when the working directory pathname contains   spaces
References: <4B5FA03C DOT 8020504 AT monai DOT ca> <4B5FC41E DOT 6090301 AT users DOT sourceforge DOT net>
In-Reply-To: <4B5FC41E.6090301@users.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On 2010/01/26 8:42 PM, Yaakov (Cygwin/X) wrote:
> On 26/01/2010 20:09, Steven Monai wrote:
>> $ pwd
>> /home/steve/My Documents/bglibs
> 
> This is not a bug in cygport per se.  Spaces in paths is just a bad idea
> when you're dealing with shell scripts and you will find all sorts of
> breakage as a result (as has already been well documented on this list).

Imagine if a program like 'cp' failed because the current working
directory has a pathname that contains spaces. You'd probably agree with
me that 'cp' had a rather serious flaw, wouldn't you?

I stand by my original report. This is a bug. Not a serious show-stopper
by any stretch, but a bug, nonetheless.

When I find the time and motivation, I may try my hand at fixing it
myself. I'll report back with patches if I do.

-SM
--

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple