From owner-freebsd-hackers Tue Oct 2 11:44:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bogslab.ucdavis.edu (bogslab.ucdavis.edu [169.237.68.34]) by hub.freebsd.org (Postfix) with ESMTP id 7686E37B406 for ; Tue, 2 Oct 2001 11:44:19 -0700 (PDT) Received: from thistle.bogs.org (thistle.bogs.org [198.137.203.61]) by bogslab.ucdavis.edu (8.9.3/8.9.3) with ESMTP id LAA93189 for ; Tue, 2 Oct 2001 11:44:05 -0700 (PDT) (envelope-from greg@bogslab.ucdavis.edu) Received: from thistle.bogs.org (localhost [127.0.0.1]) by thistle.bogs.org (8.11.3/8.11.3) with ESMTP id f92IfVS07537 for ; Tue, 2 Oct 2001 11:41:37 -0700 (PDT) (envelope-from greg@thistle.bogs.org) Message-Id: <200110021841.f92IfVS07537@thistle.bogs.org> To: hackers@FreeBSD.ORG X-To: void X-Sender: owner-freebsd-hackers@FreeBSD.ORG Subject: Re: ALT- (Was: how to make 'for' understand two words as a single argumen) In-reply-to: Your message of "Tue, 02 Oct 2001 18:55:18 BST." <20011002185518.A335@firedrake.org> Reply-To: gkshenaut@ucdavis.edu Date: Tue, 02 Oct 2001 11:41:31 -0700 From: Greg Shenaut Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011002185518.A335@firedrake.org>, void cleopede: >On Tue, Oct 02, 2001 at 07:19:37AM -0700, Greg Shenaut wrote: >> >> Is there any reason why the "unbreakable space" (0xa0) shouldn't be >> the only kind of space character used/allowed in filenames? > >Any character except for '/' is allowed in filenames, and I believe it's >been that way since the dawn of time. Yes, but I mention it because if 0xa0 were used instead of space in filenames, then they wouldn't be split into several arguments and nothing special would need to be done in "for x in * ;" loops or elsewhere to handle them, but the names would still look the same to users. I just throw out the idea--as for where to enforce such a convention, I agree that the file-system definition may not be the best place, but it might be the *easiest* place (spaces could be silently mapped to 0xa0's). Greg Shenaut To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message