From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucio De Re To: 9fans@cse.psu.edu Subject: Re: [9fans] spaces in file/dir names? (and acme)? Message-ID: <20020531065327.W22942@cackle.proxima.alt.za> References: <50dde53c4ee179b167e800824a3e6d8f@collyer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <50dde53c4ee179b167e800824a3e6d8f@collyer.net>; from Geoff Collyer on Thu, May 30, 2002 at 11:13:17AM -0700 Date: Fri, 31 May 2002 06:53:27 +0200 Topicbox-Message-UUID: a2dd5c32-eaca-11e9-9e20-41e7f4b1d025 On Thu, May 30, 2002 at 11:13:17AM -0700, Geoff Collyer wrote: > > Vowels at least don't bugger parsing and don't require the use of > quoting schemes, which will become increasingly complicated to deal > with embedded spaces, newlines, slashes, and NUL bytes, and which will > make hex file names look appealing. Vowels can stay. ? Specially as there are two vowels in the conventional representation of hex values. But no lower case letters, please. (for the humour impaired, insert smiling face here - my mailer is still antidiluvian). ++L