The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Old screen editors
Date: Tue, 29 Mar 2022 16:40:25 -0400 (EDT)	[thread overview]
Message-ID: <20220329204025.6C67318C075@mercury.lcs.mit.edu> (raw)

    > From: Clem Cole

    > Ward had a nice history here:  TecoEditor
    > <http://c2.com/wiki/remodel/?TecoEditor> - worth reading

Yeah, pretty good. A couple of minor points:

"TECO Madness -- a moment of convenience, a lifetime of regret" - I
have seen this attributed to Dave Moon.

"the [ITS] version of TECO was used by Richard Stallman to implement the
original Emacs Editor" - accurate if read _just_ the right way, but incorrect
in the 'naive' reading.

Stallman didn't _originate_ the body of stuff that eventually turned into ITS
EMACS, although he did take over maintenance of it once it was rolling; and
later wrote Gnu Emacs from scratch himself.

The mostly accurate one-line history is the one given in Dan Weinreb's blog
"the original (TECO-based) Emacs was created and designed by Guy L. Steele
Jr. and David Moon. After they had it working, and it had become established
as the standard text editor at the AI lab, Stallman took over its
maintenance", to which Moon added "in all fairness I have to say that
Stallman greatly improved Emacs after he 'liberated' it from Guy and me".
More people were involved than Moon, Steele and Stallman, though; a lot of
people were writing stuff before Stallman took over; and even after that,
others (like Eugene Ciccarelli, a member of the CSR group) helped a lot with
ITS EMACS.

Stallman's EMACS paper ("sEMACS: The Extensible, Customizable,
Self-Documenting Display Editor") contains _many_ statements that are
_demonstrably_ wrong, e.g. "it is simply impossible to implement an extensible
system in [languages like PASCAL or C]" ... "This eliminates most popular
programming languages except LISP, APL and SNOBOL." Given that I've been using
a heavily customized Epsilon for decades, which is written completely in EEL
(a dialect of C enhanced with editing primitives like buffers, etc), that's
clerly very confused.

    Noel

             reply	other threads:[~2022-03-29 20:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 20:40 Noel Chiappa [this message]
2022-03-29 20:50 ` Phil Budne
2022-03-29 20:54 ` Ron Natalie
2022-03-30  5:41   ` Lars Brinkhoff
2022-03-30  7:50     ` Thomas Paulsen
  -- strict thread matches above, loose matches on Subject: below --
2022-03-29 19:09 Steve Simon
2022-03-29 21:46 ` Ron Natalie
2022-03-30  0:22   ` Tom Lyon via TUHS
2022-03-29 18:35 Noel Chiappa
2022-03-29 10:39 Noel Chiappa
2022-03-29 11:05 ` Rob Pike
2022-03-29 13:37 ` Clem Cole
2022-03-29 15:43 ` Angelo Papenhoff
2022-03-30  5:36 ` Lars Brinkhoff
2022-03-28 21:03 [TUHS] Alive? Warren Toomey via TUHS
2022-03-28 22:24 ` Bakul Shah
2022-03-28 23:23   ` Greg 'groggy' Lehey
2022-03-29  0:00     ` Bakul Shah
2022-03-29  0:31       ` [TUHS] Old screen editors Lawrence Stewart
2022-03-29  0:53         ` Charles H Sauer (he/him)
2022-03-29  8:29           ` Rob Pike
2022-03-29 13:24             ` Clem Cole
2022-03-29  8:34           ` George Michaelson
2022-03-29  8:40             ` arnold
2022-03-29 13:45               ` Clem Cole
2022-03-29 14:31                 ` Andrew Hume
2022-03-29 14:35                   ` arnold
2022-03-29 14:42                     ` Andrew Hume
2022-03-30  0:59                       ` Mary Ann Horton
2022-03-30  5:11                       ` arnold
2022-03-29 12:45         ` Thomas Paulsen
2022-03-29 13:26           ` arnold
2022-03-30  8:37         ` Ralph Corderoy

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=20220329204025.6C67318C075@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@minnie.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).