delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=2.5 required=5.0 tests=AWL,BAYES_00,BOTNET |
X-Spam-Check-By: | sourceware.org |
Message-id: | <4B732455.9080106@cygwin.com> |
Date: | Wed, 10 Feb 2010 16:25:41 -0500 |
From: | "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com> |
Reply-to: | cygwin AT cygwin DOT com |
User-Agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 |
MIME-version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Bug: cygport fails when the working directory pathname contains spaces |
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> <loom DOT 20100210T214518-631 AT post DOT gmane DOT org> |
In-reply-to: | <loom.20100210T214518-631@post.gmane.org> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
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 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |