From: bwc@borf.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: mounting Plan9 fs on linux
Date: Wed, 14 Jun 2000 14:48:37 -0400 [thread overview]
Message-ID: <200006141849.OAA22913@cse.psu.edu> (raw)
I hacked the Seventh Edition Ed many years ago to include
the `b' command and left vi(1) behind. I used ed from 1984
until 1995 when I could use sam(1). I think that people who
have have never lived on ed for any length of time have missed
out.
Brantle Coile
------ original message follows ------
From cse.psu.edu!owner-9fans Wed Jun 14 12:57:53 EDT 2000
Received: from cse.psu.edu (majordom@claven.cse.psu.edu [130.203.3.50])
by new.borf.com (8.8.8/8.8.8) with ESMTP id MAA08722;
Wed, 14 Jun 2000 12:49:51 -0400 (EDT)
Received: from localhost (majordom@localhost)
by cse.psu.edu (8.8.8/8.8.8) with SMTP id MAA18268;
Wed, 14 Jun 2000 12:54:53 -0400 (EDT)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Wed, 14 Jun 2000 12:54:47 -0400
Received: (from majordom@localhost)
by cse.psu.edu (8.8.8/8.8.8) id MAA18238
for 9fans-outgoing; Wed, 14 Jun 2000 12:54:42 -0400 (EDT)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from plan9.cs.bell-labs.com (plan9.bell-labs.com [204.178.31.2])
by cse.psu.edu (8.8.8/8.8.8) with SMTP id MAA18233
for <9fans@cse.psu.edu>; Wed, 14 Jun 2000 12:54:33 -0400 (EDT)
Message-Id: <200006141654.MAA18233@cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: mounting Plan9 fs on linux
From: "rob pike" <rob@plan9.bell-labs.com>
Date: Wed, 14 Jun 2000 12:54:11 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-9fans@cse.psu.edu
Reply-To: 9fans@cse.psu.edu
Precedence: bulk
I've even ported the plan 9 version of
ed (which is the best of the true descendants of the
original ed) back to UNIX, and run it at work on IRIX
and at home on freeBSD.
The penny drops: the b command and elisions of terminal
slashes are now in open source! That didn't take long;
just 24 years?
In another 24 years, programmers will learn how to use malloc.
-rob
next reply other threads:[~2000-06-14 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 18:48 bwc [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-31 16:08 dhog
2000-08-02 5:37 ` nigel
2000-08-02 8:38 ` Boyd Roberts
2000-07-31 10:13 forsyth
2000-08-02 5:35 ` nigel
2000-08-02 8:37 ` Boyd Roberts
2000-07-28 13:39 nigel
2000-07-31 9:07 ` Andy Newman
2000-06-14 16:54 rob pike
2000-06-12 9:58 [9fans] " CLint Davis
2000-06-14 8:52 ` [9fans] " Douglas A. Gwyn
[not found] ` <DAGwyn@null.net>
2000-06-14 16:30 ` Tom Duff
2000-07-28 12:14 ` Harri Haataja
2000-07-28 11:52 ` Boyd Roberts
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=200006141849.OAA22913@cse.psu.edu \
--to=bwc@borf.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).