The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Erik E. Fair" <>
To: The Eunuchs Hysterical Society <>
Subject: [TUHS] Re: emacs
Date: Thu, 03 Aug 2023 19:26:52 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

I first learned original TECO-based EMACS on the Stanford CERAS DECsystem-20/60 running TOPS-20 during the summer of 1978 - I'd been using line-editors before that, and EMACS was a revelation. Heck, "intelligent" (CRT) terminals were a terrific replacement for teletypes, DECwriters, and "glass" TTYs.

When I got to UCB in the fall of 1980, it took until Winter quarter (1981) to get an account on the Cory Hall (EECS) PDP-11/70 running 2.8 BSD Unix, through the Berkeley Computer Club. The Warren Montgomery emacs was available, and since I already knew emacs keystrokes, that was my editor of choice ... initially. I converted to vi because I really hated having one finger on the CTRL key all day long.

It was also nice that the BSD tty line discpline displays what you type along the same lines as TOPS-20 did, including word-erase, though trying to use ^W that way in most emacs absolutely violates the Principle of Least Astonishment ... which if you've ever interacted with rms, should not really surprise given what he did with ^S, ^Q, and ^H.

Emacs has been available (in one form or another) on Unix for a very long time.


  reply	other threads:[~2023-08-04  2:27 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 [this message]
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
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 \ \ \ \

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