From: "matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] blanks in file names
Date: Tue, 2 Jul 2002 12:53:16 +0100 [thread overview]
Message-ID: <003d01c221bf$0dfd9d30$6501a8c0@xpire> (raw)
In-Reply-To: <20020702110848.F30EA19992@mail.cse.psu.edu>
> 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
next prev parent reply other threads:[~2002-07-02 11:53 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 11:09 forsyth
2002-07-02 11:53 ` matt [this message]
2002-07-02 13:29 ` Boyd Roberts
2002-07-02 14:57 ` FJ Ballesteros
2002-07-02 16:23 ` Lucio De Re
2002-07-03 19:21 ` rob pike, esq.
2002-07-03 14:31 ` FJ Ballesteros
2002-07-02 18:28 ` plan9
2002-07-03 13:54 ` arisawa
2002-07-03 14:24 ` FJ Ballesteros
2002-07-03 19:40 ` rob pike, esq.
2002-07-03 22:10 ` arisawa
2002-07-04 8:30 ` Ralph Corderoy
-- strict thread matches above, loose matches on Subject: below --
2002-07-15 4:03 Geoff Collyer
2002-07-15 14:53 ` Jack Johnson
2002-07-21 19:52 ` Dave
2002-07-21 19:47 ` Dave
2002-07-14 18:28 rob pike, esq.
2002-07-11 23:56 okamoto
2002-07-11 8:39 Geoff Collyer
2002-07-14 18:13 ` Dave
2002-07-11 5:50 okamoto
2002-07-11 1:41 anothy
[not found] ` <"anothy@cosym.net"@Jul>
2002-07-11 6:47 ` Dave
2002-07-10 18:27 David Gordon Hogan
2002-07-10 20:56 ` arisawa
2002-07-10 8:00 Fco.J.Ballesteros
2002-07-09 7:54 Fco.J.Ballesteros
2002-07-09 1:08 okamoto
2002-07-08 23:19 David Gordon Hogan
2002-07-08 23:30 ` Dave
2002-07-08 20:22 rob pike, esq.
2002-07-08 21:21 ` Dave
2002-07-08 23:27 ` Dan Cross
2002-07-08 23:30 ` Dan Cross
2002-07-08 12:18 forsyth
[not found] ` <"forsyth@caldo.demon.co.uk"@Jul>
2002-07-08 20:42 ` Dave
2002-07-08 8:59 Fco.J.Ballesteros
[not found] ` <Fco.J.Ballesteros@Jul>
2002-07-08 20:18 ` Dave
2002-07-09 15:23 ` Dave
2002-07-10 16:02 ` Dave
2002-07-10 20:59 ` FJ Ballesteros
2002-07-10 21:51 ` Dave
2002-07-10 22:22 ` Dan Cross
2002-07-10 23:01 ` Dave
2002-07-11 2:00 ` Dan Cross
2002-07-11 6:14 ` Dave
2002-07-11 6:38 ` Lucio De Re
2002-07-14 18:00 ` Dave
2002-07-11 13:14 ` arisawa
2002-07-12 12:28 ` arisawa
2002-07-11 16:23 ` Dan Cross
2002-07-11 10:43 ` Ish Rattan
2002-07-14 18:49 ` Dave
2002-07-08 0:38 Scott Schwartz
2002-07-07 5:59 Geoff Collyer
2002-07-05 19:21 David Gordon Hogan
2002-07-05 19:52 ` Jim Choate
2002-07-05 20:10 ` Mark Bitting
2002-07-05 18:26 Sape Mullender
2002-07-05 18:23 David Gordon Hogan
2002-07-05 1:21 okamoto
[not found] <20020703160003.27491.58783.Mailman@psuvax1.cse.psu.edu>
2002-07-04 23:35 ` Andrew Simmons
2002-07-04 22:42 ` Sam
2002-07-04 22:44 ` Sam
2002-07-08 16:14 ` ozan s yigit
2002-07-04 12:26 Fco.J.Ballesteros
2002-07-04 12:20 forsyth
2002-07-04 11:37 Fco.J.Ballesteros
2002-07-04 11:36 rog
2002-07-04 9:50 Fco.J.Ballesteros
2002-07-04 9:41 forsyth
2002-07-04 8:31 Fco.J.Ballesteros
2002-07-04 8:22 forsyth
2002-07-04 7:53 Fco.J.Ballesteros
2002-07-04 7:47 Fco.J.Ballesteros
2002-07-04 6:34 forsyth
2002-07-04 7:39 ` Lucio De Re
2002-07-04 9:32 ` Nikolai SAOUKH
2002-07-03 8:00 Fco.J.Ballesteros
2002-07-03 12:00 ` Lucio De Re
2002-07-03 19:39 ` rob pike, esq.
2002-07-07 4:02 ` Dave
2002-07-07 5:17 ` arisawa
[not found] ` <"arisawa@ar.aichi-u.ac.jp"@Jul>
2002-07-07 5:38 ` Dave
2002-07-07 6:04 ` arisawa
2002-07-07 7:16 ` arisawa
2002-07-07 16:11 ` Dave
2002-07-07 16:12 ` Dave
2002-07-10 21:58 ` Dave
2002-07-10 22:38 ` arisawa
2002-07-11 5:10 ` Dave
2002-07-14 18:32 ` Dave
2002-07-14 18:51 ` Jim Choate
2002-07-14 23:27 ` arisawa
2002-07-08 9:48 ` Boyd Roberts
2002-07-08 20:22 ` Dave
2002-07-09 8:24 ` Boyd Roberts
2002-07-09 15:25 ` Dave
2002-07-08 23:05 ` Berry Kercheval
2002-07-02 18:14 rog
2002-07-02 23:08 ` Dan Cross
2002-07-02 9:53 Fco.J.Ballesteros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003d01c221bf$0dfd9d30$6501a8c0@xpire' \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).