The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Alec Muffett <alec.muffett@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Michael Siegel <msi@malbolge.net>
Subject: Re: [TUHS] Origins and life of the pg pager
Date: Mon, 15 Jun 2020 03:38:25 +0100	[thread overview]
Message-ID: <CAFWeb9J0CvhSQiA7Yg8-PqU5rc6VVoDg2c2QnMc4V-GDsZSxaw@mail.gmail.com> (raw)
In-Reply-To: <20200615014732.GJ29495@mcvoy.com>

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

On Mon, 15 Jun 2020, 02:48 Larry McVoy, <lm@mcvoy.com> wrote:

>
> Yeah, but nobody used it.  pg was not invented here in a nutshell.  more(1)
> was fine, less(1) was actually an improvement.  pg(1) was a shitty also
> ran.


I thought that the whole point of "pg" was that it was a print system
filter; that you integrated it into pipelines to throw proper formfeeds
every 66 (etc) lines rather than print over the margins of DECWriters
(etc), and that it wasn't really a tool for humans.

At least, that's how it was explained to me.

-a

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

  reply	other threads:[~2020-06-15  2:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14 22:52 [TUHS] Fwd: " 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 [this message]
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
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-15  2:26 [TUHS] " Doug McIlroy
2020-06-15  2:41 ` Bakul Shah
2020-06-15  2:55   ` Larry McVoy
2020-06-15  4:26     ` Rob Pike
2020-06-15  4:27     ` Bakul Shah
2020-06-15  4:38       ` George Michaelson
2020-06-15  7:40     ` Ed Carp
2020-06-15  8:17       ` Rob Pike
2020-06-15  7:12   ` Thomas Paulsen
2020-06-15 20:25 Norman Wilson
2020-06-15 21:36 ` Rob Pike
2020-06-15 22:55   ` Henry Bent

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=CAFWeb9J0CvhSQiA7Yg8-PqU5rc6VVoDg2c2QnMc4V-GDsZSxaw@mail.gmail.com \
    --to=alec.muffett@gmail.com \
    --cc=lm@mcvoy.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).