The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: (Noel Chiappa)
Subject: [TUHS] Re: emacs
Date: Thu,  3 Aug 2023 22:17:28 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)

    > From: Will Senn

    > 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

Montgomery Emacs was the first I knew of; it started on PDP-11 UNIX.
According to:

Montgomery Emacs started in 1980 or so; here:

is a manual from May, 1981.

It had pretty full EMACS functionality, but the editor was not written in an
implementation language of any kind (like the original, and like much later
GNU Emacs); it was written in C. It did have macros for extensions, but they
were written in Emacs commands, so, like the TECO that the original was
written in, their source looks kind of like line noise. (Does anyone young
even know what line noise looks like any more? I feel so old - and I'm a
youngster compared to McIlroy!)

    > Was TECO ever on unix?

I don't think it was widespread, but there was a TECO on the PDP-11 UNIXes at
MIT; until Montgomery Emacs arrived, it was the primary editor used on those

Not that most people used TECO commands for editing; early on, they added '^R
mode' to the UNIX TECO, similar to the one on ITS TECO, and a macro package
was written for it (in TECO - so again, the source looks like line noise);
the command set was like a stripped down EMACS - about a dozen command
characters total; see the table about a page down here:

All the source, and documentation, such as it is, it available, here:

but don't even think about running it. It's written in MACRO-11, and it used
a version of that hacked at MIT to run on UNIX. To build new versions of
that, you need a special linker - written in BCPL. So you also need the UNIX
BCPL compiler.


             reply	other threads:[~2023-08-04  2:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  2:17 Noel Chiappa [this message]
2023-08-04  5:03 ` Jonathan Gray
2023-08-05  4:34 ` Jonathan Gray
  -- strict thread matches above, loose matches on Subject: below --
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
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
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

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 \ \ \ \

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