From: Mary Ann Horton Gmail <mah@mhorton.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Question about finding curses to build on v7
Date: Tue, 11 Jun 2019 08:48:45 -0700 [thread overview]
Message-ID: <9df3d45e-b817-2c17-2ec1-2f7d22e71a37@mhorton.net> (raw)
In-Reply-To: <CAC20D2OYRK1MbtQo5AZ1mpyCVXk23zKDNhNOt7Agcf-X+K568g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
Termcap and termlib from 2BSD should work fine on standard V6/V7 -
that's what they were originally written for. You don't need curses for
vi or emacs, they have their own comparable code internally. In fact,
the original 2BSD curses from Ken Arnold was basically the vi code
pulled out into a separate library.
Warren Montgomery's emacs was internal to Bell Labs and intended for
Bell Labs versions of PDP-11 UNIX, not 2BSD, although I recall it was
often ported to the Vax. I can't recall which version of UNIX they ran
in the various Computer Centers in the early 1980s when this happened,
but I doubt it was V7; probably PWB or UNIX/TS. It would have had the
Ritchie C compiler. I can't recall if it used termcap or had the
terminals hardcoded - apparently both, according to this:
https://tech-insider.org/unix/research/1983/0119.html
Mary Ann
On 6/11/19 6:43 AM, Clem Cole wrote:
> Two more thoughts...
>
> 1.) Zimmerman EMACS (a.k.a. CCA EMACS) ran on the PDP-11 originally
> when Steve wrote it at MIT. It's the closest to the original
> ITS/PDP-10 emacs of all the originals that I knew. I'm pretty sure
> he converted it to Pavel's freely available terminfo implementation at
> some point (when he was at Masscomp), but I think the original
> Zimmerman code has screwed down terminal support to a couple of
> terminals that were used at MIT. I've lost track of Steve, but I'll
> see if I can find you an email by reaching out on an Alumni list.
>
> 2.) I believe the first (joy created) termcap was in 2BSD but I don't
> think Arnold and Horton had started to pull the curses library out of
> vi yet. I think termcap itself had been but Mary Ann would be more
> authoritative than I. Check out the 2BSD, 3BSD, and 4BSD releases and
> look for the earliest versions. The C compiler is pretty much the
> same in all cases (the only issue I can think is that by 3BSD folks at
> UCB had removed dmr's 7 character variable limit), but I think curses
> should compile without too much issue on a virgin dmr V7 compiler.
> ᐧ
>
> On Tue, Jun 11, 2019 at 8:20 AM <ron@ronnatalie.com
> <mailto:ron@ronnatalie.com>> wrote:
>
> The other early "emacs" we ran before switching to gosmacs was
> JOVE--Jonathan's Own Version of Emacs.
>
>
>
[-- Attachment #2: Type: text/html, Size: 4334 bytes --]
next prev parent reply other threads:[~2019-06-11 15:49 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 [this message]
2019-06-11 17:12 ` Lars Brinkhoff
2019-06-11 17:26 ` Clem Cole
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=9df3d45e-b817-2c17-2ec1-2f7d22e71a37@mhorton.net \
--to=mah@mhorton.net \
--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).