X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Eric Backus Subject: Re: Bug: cygport fails when the working directory pathname contains spaces Date: Wed, 10 Feb 2010 20:57:29 +0000 (UTC) Lines: 20 Message-ID: References: <2BF01EB27B56CC478AD6E5A0A28931F2A68982@A1DAL1SWPES19MB.ams.acs-inc.net> <679765.96059.qm@web25502.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 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. -- Eric -- 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