Patchwork [2,of,4,STABLE] help: attempt to clarify that pager usage is not output length based

login
register
mail settings
Submitter Matt Harbison
Date May 4, 2017, 3:30 a.m.
Message ID <22e30c35e527bd4f9c7f.1493868632@Envy>
Download mbox | patch
Permalink /patch/20422/
State Accepted
Headers show

Comments

Matt Harbison - May 4, 2017, 3:30 a.m.
# HG changeset patch
# User Matt Harbison <matt_harbison@yahoo.com>
# Date 1493863523 14400
#      Wed May 03 22:05:23 2017 -0400
# Branch stable
# Node ID 22e30c35e527bd4f9c7f0f31f61b42754d849dc9
# Parent  08d31cd2ae238c5c448f7995c1393575e7f4202c
help: attempt to clarify that pager usage is not output length based

This may be too subtle of a change to get the point across, but when I first
read the original text, I thought maybe the pager would only be invoked if
writing more than a screenful.  The distinction between this and a pager that
simply exits after printing less than a screenful is important on Windows, given
the inability of `more` to color output.

Patch

diff --git a/mercurial/help/pager.txt b/mercurial/help/pager.txt
--- a/mercurial/help/pager.txt
+++ b/mercurial/help/pager.txt
@@ -1,4 +1,4 @@ 
-Some Mercurial commands produce a lot of output, and Mercurial will
+Some Mercurial commands can produce a lot of output, and Mercurial will
 attempt to use a pager to make those commands more pleasant.
 
 To set the pager that should be used, set the application variable::