X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 10 Feb 2010 16:17:33 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Bug: cygport fails when the working directory pathname contains spaces Message-ID: <20100210211733.GA23249@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <2BF01EB27B56CC478AD6E5A0A28931F2A68982 AT A1DAL1SWPES19MB DOT ams DOT acs-inc DOT net> <679765 DOT 96059 DOT qm AT web25502 DOT mail DOT ukl DOT yahoo DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Feb 10, 2010 at 08:57:29PM +0000, Eric Backus wrote: >Marco Atzeri 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. Wow. This horse is starting to get really smelly. And the flies are driving me crazy. cgf -- 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