The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>, Adam Thornton <athornton@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: emacs
Date: Thu, 3 Aug 2023 20:59:45 -0500	[thread overview]
Message-ID: <a945a773-a989-8173-0f8d-3fe968bfb30b@gmail.com> (raw)
In-Reply-To: <CANCZdfpd4MNJanUf=WQsAvQKS-jQO=ZAVYqy8UtgBsh+H4ED3Q@mail.gmail.com>

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

Nice. the Rainbow was my first working PC. I loved it. It had a math 
coprocessor (that  I upgraded), z80 and 8088, with 1MB ram (that I 
upgraded it to, from 128k), ran Autocad! MSDOS 3.10b, CP/M and it was 
the machine I used with a 300baud modem to download the pre 1.0 
slackware - kermit/xmodem through a VMS gateway to the internet - 
1993/1994. I didn't have emacs though! I think I remember Ultrix or 
something like that, but I didn't run it.

On 8/3/23 19:32, Warner Losh wrote:
>
>
> On Thu, Aug 3, 2023, 6:19 PM Adam Thornton <athornton@gmail.com> wrote:
>
>     There are certainly teco implementations for Unix, although I
>     don't know if it was ever anyone's default editor aInywhere. 
>     Indeed, there are multiple implementations: I switched from a C
>     teco implementation to pyteco in the Rubin Science Platform
>     JupyterLab implementation (its utility is of course dubious, but
>     this is part of both my nefarious plan to make Jupyter not merely
>     mean "Julia, Python, and R", but to use that "e" -- and
>     reassociate it with the "t" -- by making it mean "Julia, Python,
>     Teco, and R", and also to include an easter egg for a fellow
>     project member who is a teco fan).
>
>     The first Emacs I used was GNU emacs at already version...16 or
>     something?  In 1989, on ... I don't remember what the main system
>     I used at the UT Austin Chaos Lab was, actually; we had an SGI
>     Iris, but that wasn't the machine I did my editing on.  But by
>     1989 it was certainly well-available and established.
>
>
> We used some stripped down emacs in 1985 on the vax 11/750 running 
> 4.2bsd.   I built micro emacs for my DEC Rainbow under MS-DOS in the 
> same time period...
>
> Warner
>
>     On Thu, Aug 3, 2023 at 5:04 PM Will Senn <will.senn@gmail.com> 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
>

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

  parent reply	other threads:[~2023-08-04  1:59 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 [this message]
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
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=a945a773-a989-8173-0f8d-3fe968bfb30b@gmail.com \
    --to=will.senn@gmail.com \
    --cc=athornton@gmail.com \
    --cc=imp@bsdimp.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).