From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] starting to agree with you about blanks
Date: Thu, 4 Jul 2002 10:25:06 +0200 [thread overview]
Message-ID: <20186626cdc2e02ec791f8123554c309@plan9.escet.urjc.es> (raw)
: I would vote for such a feature. The kernel and 9P would be freed
: of filename shackles, the shim would apply the existing rules.
: Imagine, for example, a shim that would enable a 2nd Edition
: application to access the 4th Edition filesystem. Mapping filenames
I see. I have to say it was never my aim to open the door for
any other change. It'd be both horrible and a mess to get the kernel
translate names. I think the blank stuff is horrible enough.
: to continue with the upas/fs example, here's a function that opens a
: mailbox and returns a pathname that can be used to access the messages
: therein:
...
: openmbox("/mail/box/rog/mbox", "My\x00A0Mailbox", buf);
I now see how this would break.
And agree that by doing it in the servers (in the boundaries as you say)
it can be avoided.
Do we agree that %q is also breaking this?
Or am I mistaken?
reply other threads:[~2002-07-04 8:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20186626cdc2e02ec791f8123554c309@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).