From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <003d01c221bf$0dfd9d30$6501a8c0@xpire>
From: "matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
References: <20020702110848.F30EA19992@mail.cse.psu.edu>
Subject: Re: [9fans] blanks in file names
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Date: Tue,  2 Jul 2002 12:53:16 +0100
Topicbox-Message-UUID: bf8082f6-eaca-11e9-9e20-41e7f4b1d025


> it's not just spaces.  i have had to handle / as well, for instance.
> that might not be of interest to some, but it has occurred.

Reserved characters in filename conventions seem to me to be archaic.

I often use spaces in my filenames, they are human

The directory separator for instance is in band signalling.

If I can quote Douglas A Gwyn here * :

"For example, I take it as one more example of the evil of stealing
perfectly legitimate code values for in-band control purposes."

Being unable to use / as part of a filename is burdensome when it comes to
"interesting" file servers.

For instance one of my daydreams is the IRC fileserver with the channel name
as a directory but many many channels use / in their channel names. (In fact
many people go out of their way to cram as many special characters into IRC
channel names as possible).

I've wondered if it was possible to define the path separator on a per
process basis or something.

Perhaps you can already?

matt




*
http://groups.google.com/groups?q=in+band+group:comp.os.plan9&hl=en&lr=&ie=U
TF-8&selm=3CCE1366.EAB27A38%40null.net&rnum=2