From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3D230900.47F9A746@gsyc.escet.urjc.es>
From: FJ Ballesteros <nemo@gsyc.escet.urjc.es>
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Subject: Re: [9fans] blanks in file names
References: <20020702110848.F30EA19992@mail.cse.psu.edu>
		<003d01c221bf$0dfd9d30$6501a8c0@xpire>
		<20020702132847.A490@sigint.cs.purdue.edu> <20020703135427.6DA4919991@mail.cse.psu.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed,  3 Jul 2002 16:24:00 +0200
Topicbox-Message-UUID: c09ff216-eaca-11e9-9e20-41e7f4b1d025

I wouldn't say  this change makes the system more complex,
one thing I found after playing with this 
is that even though I made no change
to the quote stuff in the C library, programs started to
handle funny file names without relying on %q.

This is the semantics for the thing I sent before:
both touch 'a x' and touch 'a\0xa0x'
would create a file named 'a x'

Thus in both cases, ls would get
'a\0x00a0x'

Besides, foreign systems would still see 'a x'

(Im sorry, but don't know how to type Alt X 00A0 under windows,
 \x00a0 above should be read like our non-break space character).

Regarding what you say about "_", I'd still like to be able
to type "touch a_x.c". IMHO, the
 character of choice doesn't matter to much, but I think
it would be better if it's not an already used character.


arisawa@ar.aichi-u.ac.jp ha escrito:
> 
> Hello,
> 
> I prefer spaces are mapped simplly to underscores.
> Then
> term% touch 'some files'
> create some_files
> and
> term% rm 'some files'
> removes some_files
> However, I don't think these defects are practically important.
> I am rather afraid Plan9 loses simplicity.
> 
> Kenji Arisawa
> E-mail: arisawa@aichi-u.ac.jp