From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] frogs and osx
Date: Fri, 4 Jan 2008 18:31:48 +1100 [thread overview]
Message-ID: <775b8d190801032331u69725293lc35b536f2fd3b9a4@mail.gmail.com> (raw)
In-Reply-To: <E87A0939-AA5A-4D98-BB8F-871A59CF8F10@orthanc.ca>
not at all, pragmatic.excluding crap from filenames was and still is good.
if you want to vote '\r' as "not a mistake" you can. but filenames created
from buggy stuff die dead, as they should.
brucee
On Jan 4, 2008 6:24 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>
> On 2008-Jan-3, at 19:29 , Russ Cox wrote:
>
> > In addition to NUL, surely / should be illegal!
> > I certainly wouldn't want \n in file names; \r seems just too close.
>
> Pathological egregiousness?
>
> There is only one true separator, and that is '/'. In the context of
> pathnames, '/' is NUL as per C strings. NUL in pathnames is silly, but
> allowed, as per pathnames.
>
> It makes no sense, but if you can push a NUL into a pathname, you
> should deal with the result. It's a pity the intermediate code has to
> do so as well ...
>
next prev parent reply other threads:[~2008-01-04 7:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 19:46 Steve Simon
2008-01-04 2:29 ` Russ Cox
2008-01-04 6:35 ` Bruce Ellis
2008-01-04 7:24 ` Lyndon Nerenberg
2008-01-04 7:31 ` Bruce Ellis [this message]
2008-01-04 7:37 ` Lyndon Nerenberg
2008-01-04 7:45 ` Bruce Ellis
2008-01-04 7:45 ` Lyndon Nerenberg
2008-01-04 9:52 ` Bruce Ellis
2008-01-04 10:17 ` Steve Simon
2008-01-04 10:26 ` Bruce Ellis
2008-01-04 11:22 ` Pietro Gagliardi
2008-02-06 13:51 ` underspecified
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=775b8d190801032331u69725293lc35b536f2fd3b9a4@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--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).