The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Greg 'groggy' Lehey <grog@lemis.com>
To: Adam Thornton <athornton@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: emacs
Date: Fri, 4 Aug 2023 10:39:43 +1000	[thread overview]
Message-ID: <20230804003943.GD64035@eureka.lemis.com> (raw)
In-Reply-To: <CAP2nic2a=FDB933Lb5bio=6DxEJSrDsbfVo5-KAOjXLU+dzS9A@mail.gmail.com>

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

On Thursday,  3 August 2023 at 17:19:10 -0700, Adam Thornton wrote:
>
> The first Emacs I used was GNU emacs at already version...16 or something?
> In 1989,

Coincidentally that's when I first used GNU Emacs on a Unix-like
system (SCO Xenix, also coincidentally in Austin).  The version was
18.51.

But as Warner says, there were plenty of Emacs-lookalikes on other
platforms, notably MINCE (MINCE Is Not Complete Emacs) on the Z-80,
which I used from 1980, and others, including the micro Emacs that
Warner used.

The Emacs lineage (TECO → GNU Emacs) isn't as straight as it might
appear.  There was also a Gosling Emacs in the interim time, and I
gather that rms used some of the concepts (screen refresh?) for GNU
Emacs.  Also I recall that the version numbering was a little
defective, something like skipping a number of major version numbers
because it seemed that enough time had passed.  But I'm hazy on the
details, and maybe somebody else can fill in.

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 http://lemis.com/broken-MUA.php

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

  parent reply	other threads:[~2023-08-04  0:39 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 [this message]
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:
  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=20230804003943.GD64035@eureka.lemis.com \
    --to=grog@lemis.com \
    --cc=athornton@gmail.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).