From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Montgomery's emacs
Date: Tue, 11 Jun 2019 13:02:54 -0400 (EDT) [thread overview]
Message-ID: <20190611170254.2DB4018C09A@mercury.lcs.mit.edu> (raw)
> From: Mary Ann Horton
> Warren's emacs would have been part of the Bell Labs 'exptools'
> (experimental tools) package ... it's possible that's what you have.
I don't think so; Warren had been a grad student in our group, and we got it
on that basis. I'm pretty sure we didn't have termcap or any of that stuff.
Noel
next reply other threads:[~2019-06-11 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 17:02 Noel Chiappa [this message]
2019-06-11 17:12 ` Clem Cole
2019-06-11 17:28 ` Brad Spencer
2019-06-11 17:55 ` Clem Cole
-- strict thread matches above, loose matches on Subject: below --
2019-06-11 15:22 Noel Chiappa
2019-06-11 15:55 ` Mary Ann Horton Gmail
2019-06-11 17:28 ` Lars Brinkhoff
2019-06-11 13:59 Pat Barron
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=20190611170254.2DB4018C09A@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).