From owner-freebsd-hackers Tue Oct 2 10:55:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id D5A3C37B405 for ; Tue, 2 Oct 2001 10:55:42 -0700 (PDT) Received: from float by dayspring.firedrake.org with local (Exim 3.22 #1 (Debian)) id 15oTlG-0000Ax-00; Tue, 02 Oct 2001 18:55:18 +0100 Date: Tue, 2 Oct 2001 18:55:18 +0100 To: gkshenaut@ucdavis.edu Cc: hackers@FreeBSD.ORG Subject: Re: ALT- (Was: how to make 'for' understand two words as a single argumen) Message-ID: <20011002185518.A335@firedrake.org> References: <200110021419.f92EJbS06989@thistle.bogs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110021419.f92EJbS06989@thistle.bogs.org> User-Agent: Mutt/1.3.18i From: void 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 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. -- Ben "An art scene of delight I created this to be ..." -- Sun Ra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message