This is the mail archive of the
mailing list for the Cygwin project.
Re: Bug: cygport fails when the working directory pathname contains spaces
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 10 Feb 2010 16:17:33 -0500
- Subject: Re: Bug: cygport fails when the working directory pathname contains spaces
- References: <2BF01EB27B56CC478AD6E5A0A28931F2A68982@A1DAL1SWPES19MB.ams.acs-inc.net> <email@example.com> <loom.20100210T214518firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Wed, Feb 10, 2010 at 08:57:29PM +0000, 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.
>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.
Wow. This horse is starting to get really smelly. And the flies are driving
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple