From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <0c9d487627fc0c8aec5d9660f18d6d6f@plan9.escet.urjc.es> To: 9fans@cse.psu.edu Subject: Re: [9fans] blanks in file names From: Fco.J.Ballesteros MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Thu, 4 Jul 2002 09:47:59 +0200 Topicbox-Message-UUID: c14cce50-eaca-11e9-9e20-41e7f4b1d025 forsyth: : the problem rob alluded to, by analogy with NAT, should not : arise within the Plan 9 system. for instance, if i have a file : of file names, can i read it in and be sure to access those names? : if space is _ and _ is `boo!' it's anyone's guess. But space is not _, space is space. As I said in a previous mail, if you have a file of file names, you can still read and use it. AFAIK, you can be sure to access those names. Nevertheless, I can understand your arguments for doing it at boundaries and not at the kernel. : should be the character in the name, the quoting approach seems : the only one that works properly, and we have some work to do : to work out all the interactions with shell scanning (oh dear!), and changing But it's not just the shell, almost *any* program reading file names would have to deal with quoting. What has been a file name is changing after %q, before that, a program would expect something like [/]a/b/..., that's no longer the case.