From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] screen editors / machine load
Date: Fri, 10 Jan 2020 10:35:26 -0500 (EST) [thread overview]
Message-ID: <20200110153526.5D0CF18C09C@mercury.lcs.mit.edu> (raw)
> When Bernie Greenberg did EMACS for Multics, he had a similar issue. I
> recall reading a document with an extensive discussion of how they dealt
> with this ... If anyone's really interested in this, and can't find it
> themselves, I can try looking for it.
I got a request for this; a Web search turned up:
https://www.multicians.org/mepap.html
which covers the points I mentioned (and more besides, such as why LISP was
chosen). I don't think this is the thing I remembered (which was, IIRC, an
informal note), but it does seem to be a later version of that.
Noel
next reply other threads:[~2020-01-10 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 15:35 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-10 14:35 Noel Chiappa
2020-01-08 7:39 [TUHS] screen editors Thomas Paulsen
2020-01-08 21:49 ` Dave Horsfall
2020-01-10 8:13 ` markus schnalke
2020-01-10 13:41 ` [TUHS] screen editors / machine load Mike Markowski
2020-01-10 13:56 ` Otto Moerbeek
2020-01-10 15:00 ` Mary Ann Horton
2020-01-10 15:48 ` Clem Cole
2020-01-10 22:18 ` Adam Thornton
2020-01-11 0:30 ` Christopher Browne
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=20200110153526.5D0CF18C09C@mercury.lcs.mit.edu \
--to=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).