The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <>
To: Will Senn <>
Cc: The Eunuchs Hysterical Society <>
Subject: [TUHS] Re: emacs
Date: Thu, 3 Aug 2023 20:44:22 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

Cantrell’s teco was pretty fast and used a lot less resources than any of
the Unix EMACS invocations.  Gosling / CMU EMACS showed up in 81 on the Vax
and is where mocklisp came from.   Zimmerman EMACS may have been earlier at
MIT but Steve sold it to CCA so it was not nearly as widespread. Noel may
know more. We got a license from CCA in ‘84 and shipped it on the Masscomp

Rms did like a number things gosling did and start to rewrite it.  (The
defaults were different from ITS was one of his issues). He released his
version around 85. FWIW:   There is still some bad blood wrt to that whole
path best I can tell.

I think there were a couple of others.

On Thu, Aug 3, 2023 at 8:04 PM Will Senn <> wrote:

> As a longtime user and lover of ed/ex/vi, I don't know much about emacs,
> but lately I've been using it more (as it seems like any self-respecting
> lisper, has to at least have a passing acquaintance with it). I recently
> went off and got MACLISP running in ITS. As part of that exploration, I
> used EMACS, but not just any old emacs, emacs in it's first incarnation as
> a set of TECO macros. To me, it just seemed like EMACS. I won't bore you
> with the details - imagine lots of control and escape sequences, many of
> which are the same today as then. This was late 70's stuff.
> My question for the group is - when did emacs arrive in unix and was it a
> full fledged text editor when it came or was it sitting on top of some
> other subssystem in unix? Was TECO ever on unix?
> Will
Sent from a handheld expect more typos than usual

[-- Attachment #2: Type: text/html, Size: 2505 bytes --]

  parent reply	other threads:[~2023-08-04  0:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  0:04 [TUHS] emacs Will Senn
2023-08-04  0:19 ` [TUHS] emacs Adam Thornton
2023-08-04  0:27   ` Rob Pike
2023-08-04  0:49     ` Larry McVoy
2023-08-04  1:00       ` Rich Salz
2023-08-04 13:25         ` Lars Brinkhoff
2023-08-04  0:32   ` Warner Losh
2023-08-04  1:23     ` Larry Stewart
2023-08-04 13:38       ` Ronald Natalie
2023-08-04  1:59     ` Will Senn
2023-08-04  2:26       ` Erik E. Fair
2023-08-04  0:39   ` Greg 'groggy' Lehey
2023-08-04  0:44 ` Clem Cole [this message]
2023-08-04  0:47   ` Clem Cole
2023-08-04  0:53   ` Warner Losh
2023-08-04  2:14   ` Dan Halbert
2023-08-04  2:18 ` Bakul Shah
2023-08-04  2:17 Noel Chiappa
2023-08-04  5:03 ` Jonathan Gray
2023-08-05  4:34 ` Jonathan Gray
2023-08-04  2:36 Noel Chiappa
2023-08-04  2:42 ` Rob Pike
2023-08-04 16:19 ` Clem Cole
2023-08-05  4:09   ` George Michaelson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).