From: Bakul Shah <bakul@iitbombay.org>
To: Will Senn <will.senn@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: emacs
Date: Thu, 3 Aug 2023 19:18:58 -0700 [thread overview]
Message-ID: <CCB38C69-0A1F-4E1B-89C5-FA090B679FAB@iitbombay.org> (raw)
In-Reply-To: <e03cd50a-f40a-c088-fc85-b154f49501d0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
I had ported Gosling Emacs to Fortune System in 1981 or 82. It was painfully slow. I vaguely remember that was due to bitfields use, for which our C compiler (pcc based IIRC) did not generate good code. I gave up at that point as it was a side project & vi was more than good enough. Earlier I had used TECO (logged in to ITS from an IMP @ USC) but not emacs.
> On 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: 1795 bytes --]
next prev parent reply other threads:[~2023-08-04 2:19 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
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 [this message]
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=CCB38C69-0A1F-4E1B-89C5-FA090B679FAB@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).