From: Dan Cross <crossd@gmail.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: vi in cooked mode?
Date: Fri, 4 Nov 2022 11:18:15 -0400 [thread overview]
Message-ID: <CAEoi9W40hLtt_mWzZPosBdSpKSum8FAam2Ns40-pPuzBHS3zMA@mail.gmail.com> (raw)
In-Reply-To: <7wv8nv1apu.fsf@junk.nocrew.org>
On Fri, Nov 4, 2022 at 2:43 AM Lars Brinkhoff <lars@nocrew.org> wrote:
> Clem Cole wrote:
> > probably the next was Zimmerman (a.k.a. CCA) EMACS, then GNU hacked
> > Gosling's version (that strange trip has been discussed elsewhere and
> > I'll not add it here). Zimmer's version was 'truer' to the original
> > MIT/PDP-10 version from ITS than Gosling but Steve had built it when
> > he worked for CCA so it was licensed (which we had a Masscomp and made
> > available to our customers).
>
> I recently found a copy of CCA Emacs. It's from 1983 and does not yet
> have the Elisp extension language. CCA was bought by Rocket Software,
> so they own it now. I asked permission to put it online, but
> unfortunately they said no.
Out of curiosity, did they say why? It's hard to imagine it holds much
commercial value now. Was it some kind of IP ownership thing?
- Dan C.
next prev parent reply other threads:[~2022-11-04 15:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 19:43 [TUHS] " Diomidis Spinellis
2022-11-03 20:26 ` [TUHS] " Clem Cole
2022-11-03 20:27 ` Clem Cole
2022-11-03 20:55 ` Warner Losh
2022-11-03 21:34 ` Clem Cole
2022-11-03 22:28 ` Warner Losh
2022-11-03 22:52 ` Ron Natalie
2022-11-04 6:43 ` Lars Brinkhoff
2022-11-04 15:18 ` Dan Cross [this message]
2022-11-04 17:54 ` Lars Brinkhoff
2022-11-04 18:33 ` Ron Natalie
2022-11-04 23:42 ` Theodore Ts'o
2022-11-05 0:45 ` Dave Horsfall
2022-11-05 1:02 ` Larry McVoy
2022-11-05 1:25 ` Bakul Shah
2022-11-05 1:40 ` Larry McVoy
2022-11-05 2:31 ` Rich Salz
2022-11-05 3:44 ` Bakul Shah
2022-11-05 18:34 ` Theodore Ts'o
2022-11-05 9:29 ` Otto Moerbeek via TUHS
2022-11-04 22:13 ` Mary Ann Horton
2022-11-03 20:17 Noel Chiappa
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=CAEoi9W40hLtt_mWzZPosBdSpKSum8FAam2Ns40-pPuzBHS3zMA@mail.gmail.com \
--to=crossd@gmail.com \
--cc=lars@nocrew.org \
--cc=tuhs@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).