From: "Ronald Natalie" <ron@ronnatalie.com>
To: "The Eunuchs Hysterical Society" <tuhs@tuhs.org>
Subject: [TUHS] Re: emacs
Date: Fri, 04 Aug 2023 13:38:49 +0000 [thread overview]
Message-ID: <em7bbf1d96-bc6e-4136-b175-65cc84a721f0@1984688d.com> (raw)
In-Reply-To: <8AA44C9A-806D-4115-8A76-9A73412185F4@serissa.com>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
I started with Warren Montgomery’s EMACS. Prior to that, my entire
screen oriented experience was with INed (a variant of the Rand editor).
BRL largely switched to the free Gosling’s emacs and then later to
Unipress. I ended up working for Unipress for a few months. Oddly,
I ended up using JOVE (Johnathon’s Own Version of Emacs) because it is a
small lightweight thing to move around.
Consequently, I never used leaned vi. If there was no emacs variant on
the machine, I used ed. My employees were quite impressed by my
ability to do complex editing with ed and regular expressions there.
-Ron
[-- Attachment #2: Type: text/html, Size: 1514 bytes --]
next prev parent reply other threads:[~2023-08-04 13: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 [this message]
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
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=em7bbf1d96-bc6e-4136-b175-65cc84a721f0@1984688d.com \
--to=ron@ronnatalie.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).