The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <>
To: Aharon Robbins <>
Cc: The Eunuchs Hysterical Society <>
Subject: Re: [TUHS] user-level v1
Date: Mon, 16 Sep 2019 10:40:09 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Mon, Sep 16, 2019 at 2:03 AM <> wrote:

> No, Bill Joy did vi.  Ken Arnold did curses.  The vi code did all it's
> stuff directly with the termlib library calls.
Both of those statements are true.  But the other truth is that Ken took
the code from vi to create the original curses library.

You are correct, vi did not use curses as a library.  It was hard coded.

Similarly, termcap started out the same way.   In fact, I know Cornell's
fred and I thought a number of other early Unix screen editors like the
original Rand e, were hardcoded for specific terminals (I personally put
the code for the Lsi and Fox into Fred which was what we mostly had at
CMU).   As UCB got more and more different displays, the routines for
terminal control also got pulled out and put into a separate library.  Mary
Ann eventually became the main person behind it and I'll let her add the
details of who did what (I'm under the impression, wnj did the first cut of
termlib and then Mary Ann overhauled it).

[-- Attachment #2: Type: text/html, Size: 1843 bytes --]

      reply	other threads:[~2019-09-16 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 16:17 Doug McIlroy
2019-09-15 20:11 ` Warren Toomey
2019-09-15 22:09   ` Dave Horsfall
2019-09-15 23:15     ` Clem cole
2019-09-16  6:03       ` arnold
2019-09-16 14:40         ` Clem Cole [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).