From: G. David Butler gdb@dbSystems.com
Subject: [9fans] allowing space (ASCII 0x20) in file names
Date: Wed, 8 Apr 1998 11:56:33 -0500 [thread overview]
Message-ID: <19980408165633.Z39Aa_bzsAePMKlGCy8jKRO-_ySMUMysZ8yKLL6PX3U@z> (raw)
Why is the space (ASCII 0x20) excluded from file names? This is done
both in /sys/src/9/port/chan.c and /sys/src/fs/port/dentry.c.
/sys/src/fs/port/dentry.c disallows <= 0x20.
/sys/src/9/port/chan.c disallows <= 0x20, '/' (for obvious reasons)
and 0x7f (not so obvious).
Is the idea to disallow unprintables?
I was just looking at IMAP (RFC2060), and it specifies modified
UTF-7 for mailbox names. The only incompatability is the ASCII
space (0x20).
So, I was wondering, is there a problem allowing the space?
P.S. I plagiarized the idea for this sig from another, but it is cute.
-------------------------------------------------------------------
G. David Butler | Who I? Zathras, a Plan9er. Nobody uses Zathras'
| system, but Zathras not mind. Zathras used to
| having others ignore Zathras. Besides, Zathras
gdb@dbSystems.com | have best system, so Zathras happy.
next reply other threads:[~1998-04-08 16:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-08 16:56 G.David [this message]
1998-04-08 17:08 Russ
1998-04-08 17:45 Tom
1998-04-08 19:58 G.David
1998-04-08 20:32 Russ
1998-04-08 21:54 G.David
1998-04-08 22:05 Rob
1998-04-08 23:56 G.David
1998-04-09 3:10 G.David
1998-04-09 22:08 G.David
1998-04-09 23:44 Tom
1998-04-10 1:03 G.David
1998-04-10 4:04 geoff
1998-04-10 14:43 forsyth
1998-04-10 14:49 G.David
1998-04-12 3:27 ozan
1998-04-13 6:00 geoff
1998-04-13 13:50 G.David
1998-04-13 23:03 geoff
1998-04-14 5:33 forsyth
1998-04-14 6:24 forsyth
1998-04-14 6:38 Nigel
1998-04-14 9:08 Elliott.Hughes
1998-04-14 9:50 Elliott.Hughes
1998-04-14 13:04 Russ
1998-04-14 13:35 Elliott.Hughes
1998-04-14 13:50 Rob
1998-04-14 15:16 Tom
1998-04-14 15:18 Russ
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=19980408165633.Z39Aa_bzsAePMKlGCy8jKRO-_ySMUMysZ8yKLL6PX3U@z \
--to=9fans@9fans.net \
/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).