The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: mah@mhorton.net (Mary Ann Horton)
Subject: [TUHS] PWB contributions
Date: Mon, 09 Nov 2015 14:12:42 -0800	[thread overview]
Message-ID: <20151109141242.156630m1mbtw4ifu@webmail.mhorton.net> (raw)
In-Reply-To: <65204902-BAB1-4624-8D14-A65BEC60A574@ccc.com>

My recollection matches Clem's - I was there and I thought Eric wrote "more".
Dan was definitely there and he might have done the first version, but  
I don't recall that.  I do recall the story about MIT, and I sure that  
ITS was the inspiration.  And I recall Eric noting the space bar was  
the "next page" key (as opposed to Return which other programs  
expected) because it's the biggest key on the keyboard.

I can't take credit for pulling libtermcap (originally libtermlib) out  
of vi, Bill Joy had already done that before I took on vi and termcap.

   Mary Ann

Quoting Clem cole <clemc at ccc.com>:

> Interesting. If I run Into Eric any time soon I'll have to ask him.   
> As I recall I don't remember Dan's version but I do remember Eric's.  
> Nor do I remember Geoff hacking on it. Plus if you look at the CSRG  
> db from Kirk, the DB shows Eric as the creator. What's more Dan's  
> name is not in the man page - Eric's is.
>
>
>
> I wonder if this is a case where Dan wrote something specific for  
> the ADM's and the 11s and Eric did something similar more general  
> around the sametime.  FWIW: Eric had always claimed to me that he  
> wrote it and it is my memory that I got the sources from him for our  
> systems in the CAD group in Cory hall (and have never had a reason  
> to doubt him in that claim).
>
> I do remember more(1) was was one of the first programs that used  
> Hortons termcap library that he had pulled out of joy's vi and  
> greatly enhanced.  (Ken) Arnold then took it and created curses (for  
> Rogue actually).




  parent reply	other threads:[~2015-11-09 22:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09  1:39 Doug McIlroy
2015-11-09  1:48 ` John Cowan
2015-11-09  2:12 ` Clement T. Cole
2015-11-09  2:54   ` Win Treese
2015-11-09  2:58     ` Win Treese
2015-11-09  3:36       ` Clem cole
2015-11-09  3:51         ` Clem cole
2015-11-09 15:40         ` Dave Horsfall
2015-11-09 15:54           ` Clem Cole
2015-11-09 22:12         ` Mary Ann Horton [this message]
2015-11-09  3:38       ` Random832
2015-11-09  4:50         ` Clem cole
2015-11-09 13:58   ` Doug McIlroy
2015-11-09 14:02     ` Ronald Natalie
2015-11-09 14:44     ` John Cowan
2015-11-10 20:26     ` [TUHS] A portrait of cut(1) (was: PWB contributions) markus schnalke
2015-11-10 22:10       ` Clem Cole
2015-11-10 23:10       ` Andy Kosela
2015-11-10 23:12         ` John Cowan
2015-11-10 23:34           ` Larry McVoy
2015-11-10 23:39             ` John Cowan
2015-11-11  0:16       ` [TUHS] A portrait of cut(1) Random832
2015-11-11 12:23         ` markus schnalke
2015-11-09 22:23   ` [TUHS] PWB contributions Jeremy C. Reed
2015-11-10  4:11     ` Random832
2015-11-09  4:44 ` Larry McVoy
2015-11-09  4:51   ` John Cowan
2015-11-09  5:07     ` Larry McVoy
2015-11-09  5:09       ` Larry McVoy
2015-11-09  5:16         ` John Cowan
2015-11-09  5:16         ` Leonardo Taccari
2015-11-09  2:14 Doug McIlroy
2015-11-09  2:32 ` John Cowan

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=20151109141242.156630m1mbtw4ifu@webmail.mhorton.net \
    --to=mah@mhorton.net \
    /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).