Bug: cygport fails when the working directory pathname contains spaces

[Larry Hall (Cygwin)]

On 02/10/2010 03:57 PM, Eric Backus wrote:
> Marco Atzeri<marco_atzeri<at>  yahoo.it>  writes:
>
>> Don't use filename with a space inside is a WELL KNOWN
>> rule of any UNIX system.
>> If MS made a stupid decision, we should not follow it.
>>
>> Regards
>> Marco
>
> It really doesn't matter to me whether cygport supports filenames with
> spaces.  And it is certainly true that filenames with spaces are relatively
> common on Windows systems, but relatively rare on unix systems.
>
> Nevertheless, there is no rule about this.  Actually I believe POSIX allows
> filenames to have *any* character in them except a directory separator '/' or
> a terminating null '\0'.  It is well known that *robust* scripts should use
> proper quoting to allow for things like spaces in filenames.

I think this is an old enough and dead enough thread to just let it lie.  If
you'd really like to pursue this on general principles, please find another
forum to argue the merits.  You don't want to be accused of trolling the
Cygwin list looking for old topics to incite thread-wars over after all.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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