From: Uriel <uriel99@gmail.com>
To: lucio@proxima.alt.za,
"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] directly opening Plan9 devices
Date: Sun, 4 Jan 2009 14:01:43 +0100 [thread overview]
Message-ID: <5d375e920901040501pb75aceat3129486817f8cbb1@mail.gmail.com> (raw)
In-Reply-To: <d22433c53465761de8474fa94c216a84@proxima.alt.za>
As I read it, rob seems to disagree with you:
> # file names were just a hack to get started - literally to get started.
They were a place holder until a better idea came along. None has.
>
> # was never considered a great idea; I just needed some way to
name an unnamed resource. I deliberately chose # as the character
because it's the comment character in the shell and therefore is
really irritating to use.
http://9fans.net/archive/2003/02/832
Still, clearly to this day nobody has come up with a fully
satisfactory design to replace #, and certainly not an implementation
of any such design.
Seems that despite the many years of thinking, this is still a tricky
problem, and # has turned out to be 'good enough' to keep any
alternative from appearing.
Peace
uriel
On Sun, Jan 4, 2009 at 12:41 PM, <lucio@proxima.alt.za> wrote:
>> No one has yet offered a working, cleaner idea.
>
> I think it is a working, perfectly clean idea, myself. It's a
> namespace of its own and there are only a very few inconsistencies
> within it, well justified by the very nature of the namespace. That
> minor nits such as #s and #| being a bit off the paradigm apply
> suggests that some aspects could be given more thought, but they do
> not invalidate the usefulness and consistency of the design. Rather,
> they show a surprising maturity for something that probably did not
> get too many iterations.
>
> ++L
>
>
>
next prev parent reply other threads:[~2009-01-04 13:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 21:44 Roman V. Shaposhnik
2009-01-03 21:46 ` erik quanstrom
2009-01-03 21:56 ` Roman V. Shaposhnik
2009-01-03 22:03 ` erik quanstrom
2009-01-03 22:40 ` Roman V. Shaposhnik
2009-01-03 22:46 ` Francisco J Ballesteros
2009-01-03 22:56 ` erik quanstrom
2009-01-04 5:00 ` Roman V. Shaposhnik
2009-01-04 5:40 ` erik quanstrom
2009-01-04 4:58 ` Roman V. Shaposhnik
2009-01-03 22:57 ` erik quanstrom
2009-01-03 23:15 ` Russ Cox
2009-01-03 23:17 ` erik quanstrom
2009-01-04 5:07 ` Roman V. Shaposhnik
2009-01-04 5:05 ` Roman V. Shaposhnik
2009-01-03 22:21 ` Francisco J Ballesteros
2009-01-03 22:40 ` erik quanstrom
2009-01-04 5:12 ` Roman V. Shaposhnik
2009-01-04 5:27 ` erik quanstrom
2009-01-04 5:39 ` lucio
2009-01-04 5:42 ` erik quanstrom
2009-01-05 0:52 ` Roman V. Shaposhnik
2009-01-05 6:21 ` Roman Zhukov
2009-01-05 11:00 ` Charles Forsyth
2009-01-06 5:02 ` Roman Shaposhnik
2009-01-06 14:17 ` erik quanstrom
2009-01-07 16:55 ` ron minnich
2009-01-07 17:16 ` erik quanstrom
2009-01-08 5:13 ` ron minnich
2009-01-08 13:37 ` erik quanstrom
2009-01-08 14:03 ` Charles Forsyth
2009-01-08 15:36 ` ron minnich
2009-01-08 15:44 ` erik quanstrom
2009-01-08 17:34 ` Roman V. Shaposhnik
2009-01-08 17:35 ` Charles Forsyth
2009-01-08 7:45 ` Dave Eckhardt
2009-01-08 17:43 ` Roman V. Shaposhnik
2009-01-08 23:30 ` Roman V. Shaposhnik
2009-01-04 7:01 ` Russ Cox
2009-01-04 11:41 ` lucio
2009-01-04 13:01 ` Uriel [this message]
2009-01-04 13:16 ` lucio
2009-01-05 0:41 ` Roman V. Shaposhnik
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=5d375e920901040501pb75aceat3129486817f8cbb1@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).