From mboxrd@z Thu Jan 1 00:00:00 1970 From: "rob pike, esq." To: 9fans@cse.psu.edu Subject: Re: [9fans] blanks in file names Message-ID: <447280.1025709673@GOLD> In-Reply-To: <3D21BF4E.9A3A6A39@gsyc.escet.urjc.es> References: <3D21BF4E.9A3A6A39@gsyc.escet.urjc.es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Date: Wed, 3 Jul 2002 15:21:14 -0400 Topicbox-Message-UUID: c090b0ee-eaca-11e9-9e20-41e7f4b1d025 Because file names come in places other than directories. You can't always get this right. If you translate them going into open(), you will be inconsistent with file names used other ways. It's similar to the problem with NAT boxes and hidden IP addresses. I'd say do nothing yet. There is no clear right answer. -rob --On Tuesday, July 02, 2002 4:57 PM +0200 FJ Ballesteros wrote: >> >> Some characters were just not meant to be in filenames, which would >> avoid the above. > > But they are, even in my system there're many files with blanks on their > names > (and I never choose such names). > > Since IFAIK none of the authors have anything against the proposal > that came out of 9fans (see my previous post, where I tried to summarize > it), > what if I change the source just to do it? > > - let Alt-spc generate our unicode blank character > - change the system to translate blanks in file names to the > same character. > - change the quote library so it does not quote that character. > > I don't have much time right know and that's why I ask before changing > the > code. I'm willing to implement it if there's agreement, so please, don't > ignore the proposal just becase there's no code attached by now, > just let me know.