From: Rob Pike <robpike@gmail.com>
To: Derek Fawcus <dfawcus+lists-tuhs@employees.org>
Cc: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Fwd: Origins and life of the pg pager
Date: Tue, 23 Jun 2020 07:33:31 +1000 [thread overview]
Message-ID: <CAKzdPgzR_pdZLKeGrYTNAXyyXR_=iXtJTEa3TFkOFra6e8b8+g@mail.gmail.com> (raw)
In-Reply-To: <20200622162406.GA48733@clarinet.employees.org>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
There is only one correct way.
% grep PAGER .bashrc
export PAGER='col -b'
%
-rob
On Tue, Jun 23, 2020 at 2:26 AM Derek Fawcus <
dfawcus+lists-tuhs@employees.org> wrote:
> On Sun, Jun 21, 2020 at 05:35:28PM -0700, Greg A. Woods wrote:
> >
> > In a related vein what annoys me are so-called modern programs like
> > "git", "hg", and others which default to always piping their output
> > through $PAGER, along with such things as colour decorations enabled,
> > but when you tack on "|$PAGER" to their command-line then they turn off
> > the decorations! They cause me to have to undo decades of finger
> > memory.
>
> Well, for further fun, one could always export GIT_PAGER=cat,
> then git will not use a pager for those commands, recognising that
> 'cat' is a no-op in such cases. :-)
>
> DF
>
[-- Attachment #2: Type: text/html, Size: 3834 bytes --]
next prev parent reply other threads:[~2020-06-22 21:34 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
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 [this message]
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='CAKzdPgzR_pdZLKeGrYTNAXyyXR_=iXtJTEa3TFkOFra6e8b8+g@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=dfawcus+lists-tuhs@employees.org \
--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).