From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: 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="UTF-8" Content-Transfer-Encoding: 8bit Date: Mon, 8 Jul 2002 10:59:20 +0200 Topicbox-Message-UUID: c448a174-eaca-11e9-9e20-41e7f4b1d025 I think we've lost focus. I'm scared. The whole point was to handle characters which are allowed but may cause problems like ' ' and ''''. And AFAIK, the problem was that we get them from outside systems, and that people may be so used to them that they may even start to use them on native Plan 9 files. Don't you think that changing open, considering '/' in names, and similar stuff is just too much? I'm scared. That may be interesting, but it would lead to a very different system. Moreover, do you think that the system designers would ever consider '/' as a legitimate character within file names? Although I don't know, I'd bet they'll never do that (at least I have to say I would never do it, sorry). I think I'm just going to try option bⁱ myself and then send a diff in case it works out. But above all, I will undo the changes made in this respect to my local system if you guys or the system designers choose a different way. It's a very nice system and I wouldn't like to get N different ones nor to break it. -- ⁱ Option b was: remove quoting from ls et al, add it to those that print commands, and fix those that don't cosider ' ' in file names.