From: Lars Brinkhoff <lars@nocrew.org>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Michael Siegel <msi@malbolge.net>
Subject: Re: [TUHS] Fwd: Origins and life of the pg pager
Date: Mon, 15 Jun 2020 19:08:31 +0000 [thread overview]
Message-ID: <7wh7vcm9jk.fsf@junk.nocrew.org> (raw)
In-Reply-To: <7wr1ugmix8.fsf@junk.nocrew.org> (Lars Brinkhoff's message of "Mon, 15 Jun 2020 15:45:55 +0000")
> Clem Cole wrote:
>> I think Eric arrived later than Dan (maybe a year later), but was also
>> ex-MIT, and he too had used/seen --MORE-- on ITS as Dan had. But I was
>> under the impression Eric started over.
> That's not what Dan writes (see below), but I'll ask him to confirm his
> version.
He responded and asked me to post his reply to the mailing list:
As described in https://danhalbert.org/more.html, I wrote the
original version of more. It was only a page or two or code, and was
meant to replace the dysfunctional cr3. It went into raw mode so it
could read a space as a "next page" character, but otherwise didn't
care about what kind of terminal it was on. (The ADM-3's (not 3A's)
were barely a terminal.)
Clem Cole's timeline is a bit off. Eric Shienbrood, Geoff Peck, and I
all arrived at Berkeley at the same time in fall 1978 as CS grad
students, and became friends (along with some other folks).
After I wrote the first version, I did not have time to continue to
working on it, so Eric picked it up and added many more features. My
contribution is that I had the original idea (to replace cr3) and
coined the name, and made the very first version. I am grateful to
Eric, Geoff, and others taking it much further with many more
features.
I am still in touch with Eric, and will ask him to see what he has to
say. We are both still alive so I appreciate Lars getting in touch
with me to verify.
I also wrote a hack less as a joke, which was more except that it
scrolled up the screen rather than down . I think it was Bill Joy who
then wrote another less that paged from the end of the file (and also
scrolled up the screen).
next prev parent reply other threads:[~2020-06-15 19:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 22:52 Warren Toomey
2020-06-14 23:37 ` Mary Ann Horton
2020-06-14 23:52 ` [TUHS] " David Barto
2020-06-15 0:06 ` George Michaelson
2020-06-15 0:31 ` Alan D. Salewski
2020-06-15 0:35 ` Alan D. Salewski
2020-06-15 1:38 ` Warner Losh
2020-06-15 1:47 ` Larry McVoy
2020-06-15 2:38 ` Alec Muffett
2020-06-15 2:46 ` Alec Muffett
2020-06-15 2:26 ` Charles H. Sauer
2020-06-15 14:03 ` Mary Ann Horton
2020-06-15 20:19 ` Greg A. Woods
2020-06-15 20:50 ` Mary Ann Horton
2020-06-15 0:32 ` [TUHS] Fwd: " Nemo Nusquam
2020-06-15 5:41 ` Lars Brinkhoff
2020-06-15 13:56 ` Clem Cole
2020-06-15 14:15 ` Mary Ann Horton
2020-06-15 14:56 ` Clem Cole
2020-06-15 15:04 ` Richard Salz
2020-06-15 16:14 ` Clem Cole
2020-06-15 15:45 ` Lars Brinkhoff
2020-06-15 19:08 ` Lars Brinkhoff [this message]
2020-06-21 18:49 ` Michael Siegel
2020-06-22 0:35 ` Greg A. Woods
2020-06-22 16:24 ` Derek Fawcus
2020-06-22 21:33 ` Rob Pike
2020-06-22 21:58 ` Kurt H Maier
2020-06-22 21:59 ` [TUHS] " Bakul Shah
2020-06-22 22:43 ` Steffen Nurpmeso
2020-06-25 1:50 ` Theodore Y. Ts'o
2020-06-25 21:31 ` Steffen Nurpmeso
2020-07-05 1:34 ` Dave Horsfall
2020-06-18 12:49 ` [TUHS] Fwd: " Michael Siegel
2020-06-21 22:40 Noel Chiappa
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=7wh7vcm9jk.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=clemc@ccc.com \
--cc=msi@malbolge.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).