From: Larry McVoy <lm@mcvoy.com>
To: Donald ODona <mutiny.mutiny@india.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Emacs (was: Isaacson v Unix)
Date: Sat, 5 Jan 2019 22:03:55 -0800 [thread overview]
Message-ID: <20190106060355.GP24497@mcvoy.com> (raw)
In-Reply-To: <1584792008.119344.1546754504662.JavaMail.tomcat@india-live-be04>
This is a distraction, but didn't the BDS C guy take some of those
interfaces into his editor?
On Sun, Jan 06, 2019 at 06:01:44AM +0000, Donald ODona wrote:
> teco, a very early (even earlier than qed/ed) character based editor, rather a stream editor in unix terms, was written by the student dan murphy for the pdp-1 in around 1964. In the 70ths two teco macro collections were popular in MIT's AI lab: tmacs&temacs, written by gus steele et al., leaving both packages unmaintained. rms took over maintenance, consolidating and improving them. That's all. He neither written teco nor the teco macro packages.
>
>
> At 6 Jan 2019 02:51:32 +0000 (+00:00) from Greg 'groggy' Lehey <grog@lemis.com>:
> > On Saturday, 5 January 2019 at 17:43:43 -0800, Chris Hanson wrote:
> > > On Jan 5, 2019, at 7:31 AM, Larry McVoy <lm@mcvoy.com> wrote:
> > >>
> > >> +1. RMS always talked big but the real work was done by other people.
> > >> GCC was Tiemann at Sun and then at Cygnus, groff was James Clark,
> > >> etc. I think RMS hacked on emacs but not much else.
> > >
> > > Which I thought was originally derived from Unipress emacs
> > > (Gosmacs), and was why old source code used to be hard to find.
> >
> > I don't think there's any serious doubt that rms wrote the original
> > Emacs, in TECO. If I understand it correctly, though, he took
> > significant improvements, including screen redisplay, from Gosling
> > Emacs.
> >
> > Greg
> > --
> > Sent from my desktop computer.
> > Finger grog@lemis.com for PGP public key.
> > See complete headers for address and phone numbers.
> > This message is digitally signed. If your Microsoft mail program
> > reports problems, please read <a target="_blank" href="http://lemis.com/broken-MUA">http://lemis.com/broken-MUA</a>
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2019-01-06 6:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 2:26 [TUHS] Isaacson v Unix Doug McIlroy
2019-01-05 2:35 ` Ronald Natalie
2019-01-05 15:31 ` Larry McVoy
2019-01-05 17:01 ` A. P. Garcia
2019-01-05 20:27 ` Paul Winalski
2019-01-05 21:38 ` A. P. Garcia
2019-01-05 21:51 ` Rob Pike
2019-01-05 21:53 ` Rob Pike
2019-01-05 21:52 ` Larry McVoy
2019-01-06 1:50 ` Chris Hanson
2019-01-06 2:18 ` A. P. Garcia
2019-01-05 17:07 ` Donald ODona
2019-01-05 21:20 ` joe mcguckin
2019-01-06 1:43 ` Chris Hanson
2019-01-06 2:40 ` [TUHS] Emacs (was: Isaacson v Unix) Greg 'groggy' Lehey
2019-01-06 6:01 ` Donald ODona
2019-01-06 6:03 ` Larry McVoy [this message]
2019-01-06 6:26 ` Chris Hanson
2019-01-06 7:50 ` [TUHS] Emacs Lars Brinkhoff
2019-01-06 14:23 ` Andrew Luke Nesbit
2019-01-06 14:30 ` Lars Brinkhoff
2019-01-05 9:08 ` [TUHS] Isaacson v Unix William Corcoran
2019-01-05 12:09 ` Ed Carp
2019-01-05 14:15 ` Paul Winalski
2019-01-05 15:01 ` Ed Carp
2019-01-06 4:35 ` Bakul Shah
2019-01-06 4:52 ` Bakul Shah
2019-01-06 5:00 ` Toby Thain
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=20190106060355.GP24497@mcvoy.com \
--to=lm@mcvoy.com \
--cc=mutiny.mutiny@india.com \
--cc=tuhs@tuhs.org \
/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).