From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: "Lars Brinkhoff" <lars@nocrew.org>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Old screen editors
Date: Wed, 30 Mar 2022 09:50:41 +0200 [thread overview]
Message-ID: <a066afecfb9dfa8dfc9cc77428634415@firemail.de> (raw)
In-Reply-To: <7wh77gkne5.fsf@junk.nocrew.org>
> Well, even that is a bit inaccurate. He implemented emacs by wrapping
> new code around James Gosling's (also licensed as Unipress) EMACS.
its generally very well known that RMS hired a programmer doing that. Himself, he only contributed some elisp code.
next prev parent reply other threads:[~2022-03-30 8:24 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
2022-03-30 5:41 ` Lars Brinkhoff
2022-03-30 7:50 ` Thomas Paulsen [this message]
-- 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=a066afecfb9dfa8dfc9cc77428634415@firemail.de \
--to=thomas.paulsen@firemail.de \
--cc=lars@nocrew.org \
--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).