From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Was curses ported to Seventh Edition Unix?
Date: Sat, 25 May 2024 11:25:49 -0500 [thread overview]
Message-ID: <20240525162549.yg2qndtloodv3upq@illithid> (raw)
In-Reply-To: <CAC20D2Nmqeb1_jfWQVko-vKVpXQ2yDDz00qDiKEt-=qxaoK+FQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Hi Clem,
At 2024-05-25T12:14:10-0400, Clem Cole wrote:
> Ouch -- there was no licensing issue with [BSD] curses or termcap.
Right. I wasn't trying to imply otherwise. That's why Pavel Curtis
could use BSD curses as a basis for his pcurses.
It is only System V curses that was encumbered. And now it too is
available for inspection, if in a somewhat gray area for anyone with
commercial ambitions.
> termcap and curses were written at UCB.
Agreed. I've seen no claim anywhere to the contrary.
> When MaryAnn went to Columbus - there was desire to rewrite to be
> "compiled". That work was terminfo. AT&T >>restricted<< terminfo.
Yes. This too is my understanding. terminfo is a better API (and
source format) than termcap, but I also surmise that better support for
deployment environments with large "fleets" of video terminals was also
seen by AT&T management as an enticing prospect for vendor lock-in.
> Pavel (with coaching from a few of us, including me], wrote a new
> implementation of terminfo. When he was added it, he combined a
> rewrite of curses.
Thank you for the confirmation. And for supplying some coaching all
those years ago--we're still enjoying the benefits today!
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-25 16:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 0:03 [TUHS] " G. Branden Robinson
2024-05-25 0:46 ` [TUHS] " Clem Cole
2024-05-25 0:57 ` G. Branden Robinson
2024-05-25 10:48 ` Jonathan Gray
2024-05-25 11:08 ` Arrigo Triulzi via TUHS
2024-05-25 12:16 ` Clem Cole
2024-05-25 23:06 ` Rob Pike
2024-05-25 15:06 ` [TUHS] " Douglas McIlroy
2024-05-25 15:11 ` [TUHS] " Rich Salz
2024-05-25 15:40 ` Clem Cole
2024-05-25 15:43 ` Clem Cole
2024-05-25 15:51 ` Clem Cole
2024-05-25 15:57 ` G. Branden Robinson
2024-05-25 16:06 ` Clem Cole
2024-05-25 16:13 ` G. Branden Robinson
2024-05-25 16:21 ` Clem Cole
2024-05-25 16:38 ` G. Branden Robinson
2024-05-25 17:02 ` Warner Losh
2024-05-25 16:14 ` Clem Cole
2024-05-25 16:25 ` G. Branden Robinson [this message]
2024-05-25 18:07 ` Adam Sampson
2024-05-27 18:31 ` Mary Ann Horton
2024-05-25 15:28 ` G. Branden Robinson
2024-05-25 17:24 Steve Simon
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=20240525162549.yg2qndtloodv3upq@illithid \
--to=g.branden.robinson@gmail.com \
--cc=clemc@ccc.com \
--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).