The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brad Spencer <brad@anduin.eldar.org>
To: Clem Cole <clemc@ccc.com>
Cc: tuhs@minnie.tuhs.org, jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Montgomery's emacs
Date: Tue, 11 Jun 2019 13:28:03 -0400	[thread overview]
Message-ID: <xon4l4w58ws.fsf@anduin.eldar.org> (raw)
In-Reply-To: <CAC20D2P0kV19HrfHNJ1FEWrScR5aBiZeom8iQAM0Tr6vCgd3tg@mail.gmail.com> (message from Clem Cole on Tue, 11 Jun 2019 13:12:51 -0400)

Clem Cole <clemc@ccc.com> writes:

> I thought much of the exptools went into something whos name was like the
> AT&T Unix Toolkit Library (that Summit maintained).   It was subscription
> oriented (you paid per tool, but had an unlimited license for it).  This
> was how Korn Shell for $2K and a few other things made it out of Bell - I
> think that eventually, ditroff was moved there instead of being a separate
> distribution. I've now forgotten many of the details - there was a
> build/make replacement IIRC that was there also, many of the Jerq tools and
> games like GBACA and some others were in there.  Thinking about it much of
> the support for Jerq (68000) and Teletype version (BLIT/We32000) may have
> been in the Toolkit library.
> ᐧ
>


nmake ??  I think it may have been called.  I touched something that
matches what is being called "exptools" and the like when I was at 6200
Broad St.  We used nmake and ksh extensively in the software project I
was a part of, and I know I had access to the source for an ancient
version of nmake at one point.  And I remember the subscription thing
too and I seem to recall you had to pay per architecture at least by the
time I was exposed to it.  I got the ancient nmake version compiled on
HP-UX 10.x to get part of the product I was a part of building on HP-UX
10.x.  The official HP-UX 10.x version from the subscription service was
expensive, as I remember things.

There was at least one person in the group who used a version of emacs
that was from the same, or related, source.  I never used it, as I
preferred GNU emacs.





-- 
Brad Spencer - brad@anduin.eldar.org - KC8VKS - http://anduin.eldar.org

  reply	other threads:[~2019-06-11 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 17:02 Noel Chiappa
2019-06-11 17:12 ` Clem Cole
2019-06-11 17:28   ` Brad Spencer [this message]
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=xon4l4w58ws.fsf@anduin.eldar.org \
    --to=brad@anduin.eldar.org \
    --cc=clemc@ccc.com \
    --cc=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).