From: Clem Cole <clemc@ccc.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: "Erik E. Fair" <fair@netbsd.org>, TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Question about finding curses to build on v7
Date: Tue, 11 Jun 2019 13:26:44 -0400 [thread overview]
Message-ID: <CAC20D2Px2aDZZP7gJ=M0E+qxm-Hu6GLqOy026UUA-RYbsgW_dw@mail.gmail.com> (raw)
In-Reply-To: <7wzhmoqc4z.fsf@junk.nocrew.org>
[-- Attachment #1: Type: text/plain, Size: 2168 bytes --]
Interesting and that sounds quite plausible. CCA sold it at one point.
Masscomp (because Steve was working for us) got a license and a
redistribution license. IIRC: we could redistribute the binary for free
as long as CCA got Steve's changes back.
Steve definitely did the terminfo/lib work for CCA Emacs at Masscomp, as I
had pointed out that AT&T was moving to terminfo but was locking it up
inside of the System V (AT&T 'consider it standard' stuff - much to a
number of their own people telling them not too). Pavel ?? Curtis I think
?? - I've forgotten his last name - had written a new uncontaminated
version at Cornell that was a functional replacement and that could read
the AT&T ASCII database and compile them properly. (I don't remember if
Pavel's version could take the AT&T binary versions). I had obtained
Pavel's version and we were shipping that as our terminfo/lib
implementation on the Masscomp boxes and were switching our code to use it,
as we had not yet signed a System V license and were shipping on a System
III based one. Steve started to include Pavel's library in the CCA
version, which he got from me.
ᐧ
On Tue, Jun 11, 2019 at 1:12 PM Lars Brinkhoff <lars@nocrew.org> wrote:
> Clem Cole wrote:
> > 1.) Zimmerman EMACS (a.k.a. CCA EMACS) ran on the PDP-11 originally
> > when Steve wrote it at MIT.
>
> I have this on the origin of Montgomery and Zimmerman Emacs:
>
> "[Montgomery's] emacs implementation was begun in 1979, after having
> left MIT. I made it freely available to people INSIDE of Bell Labs,
> and it was widely used. It was never officially "released" from Bell
> Labs."
>
> "Unfortunately, several copies did get out during that time, mainly
> due to people who left Bell Labs to return to school or gave copies to
> friends. When Zimmerman modified one of those copies as the original
> basis for CCA emacs, AT&T and CCA had a prolonged debate over it.
> Eventually the matter was resolved when Zimmerman replaced the last of
> my code"
>
>
> https://github.com/larsbrinkhoff/emacs-history/blob/sources/Usenet/net.emacs/btl-emacs-2.txt
>
[-- Attachment #2: Type: text/html, Size: 3254 bytes --]
next prev parent reply other threads:[~2019-06-11 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 2:52 Adam Thornton
2019-06-11 6:12 ` Erik E. Fair
2019-06-11 12:19 ` ron
2019-06-11 13:43 ` Clem Cole
2019-06-11 15:48 ` Mary Ann Horton Gmail
2019-06-11 17:12 ` Lars Brinkhoff
2019-06-11 17:26 ` Clem Cole [this message]
2019-06-11 18:05 ` Mary Ann Horton Gmail
2019-06-11 17:08 ` Lars Brinkhoff
2019-06-11 17:05 ` Lars Brinkhoff
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='CAC20D2Px2aDZZP7gJ=M0E+qxm-Hu6GLqOy026UUA-RYbsgW_dw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=fair@netbsd.org \
--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).