From: "Ron Natalie" <ron@ronnatalie.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Old screen editors
Date: Tue, 29 Mar 2022 20:54:20 +0000 [thread overview]
Message-ID: <emf2e6dee4-ef35-4352-8cfc-a51412810fcc@alien> (raw)
In-Reply-To: <20220329204025.6C67318C075@mercury.lcs.mit.edu>
>
>Stallman didn't _originate_ the body of stuff that eventually turned into ITS
>EMACS, although he did take over maintenance of it once it was rolling; and
>later wrote Gnu Emacs from scratch himself.
Well, even that is a bit inaccurate. He implemented emacs by wrapping
new code around James Gosling's (also licensed as Unipress) EMACS.
After a bit of a protracted argument, he finally wrote his own stuff to
get the infringing code out.
> that I've been using
> heavily customized Epsilon for decades, which is written completely in EEL
> dialect of C enhanced with editing primitives like buffers, etc), that's clearly very confused.
I was an Epsilon user as well.
The "self documenting" aspects of EMACS are kind of laughable as well. I'll start with using backspace for the help key and go from there :)
next prev parent reply other threads:[~2022-03-29 20:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 20:40 Noel Chiappa
2022-03-29 20:50 ` Phil Budne
2022-03-29 20:54 ` Ron Natalie [this message]
2022-03-30 5:41 ` Lars Brinkhoff
2022-03-30 7:50 ` Thomas Paulsen
-- strict thread matches above, loose matches on Subject: below --
2022-03-29 19:09 Steve Simon
2022-03-29 21:46 ` Ron Natalie
2022-03-30 0:22 ` Tom Lyon via TUHS
2022-03-29 18:35 Noel Chiappa
2022-03-29 10:39 Noel Chiappa
2022-03-29 11:05 ` Rob Pike
2022-03-29 13:37 ` Clem Cole
2022-03-29 15:43 ` Angelo Papenhoff
2022-03-30 5:36 ` Lars Brinkhoff
2022-03-28 21:03 [TUHS] Alive? Warren Toomey via TUHS
2022-03-28 22:24 ` Bakul Shah
2022-03-28 23:23 ` Greg 'groggy' Lehey
2022-03-29 0:00 ` Bakul Shah
2022-03-29 0:31 ` [TUHS] Old screen editors Lawrence Stewart
2022-03-29 0:53 ` Charles H Sauer (he/him)
2022-03-29 8:29 ` Rob Pike
2022-03-29 13:24 ` Clem Cole
2022-03-29 8:34 ` George Michaelson
2022-03-29 8:40 ` arnold
2022-03-29 13:45 ` Clem Cole
2022-03-29 14:31 ` Andrew Hume
2022-03-29 14:35 ` arnold
2022-03-29 14:42 ` Andrew Hume
2022-03-30 0:59 ` Mary Ann Horton
2022-03-30 5:11 ` arnold
2022-03-29 12:45 ` Thomas Paulsen
2022-03-29 13:26 ` arnold
2022-03-30 8:37 ` Ralph Corderoy
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=emf2e6dee4-ef35-4352-8cfc-a51412810fcc@alien \
--to=ron@ronnatalie.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.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).