[PATCH 3/6] git.1: Clarify the behavior of the --paginate option
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Feb 14, 2010, 12:02 UTC
- Message-ID
- <20100214120235.GC3499@progeny.tock>
- In-Reply-To
- <20100214115430.GA1849@progeny.tock>
The --paginate option is meant to negate the effect of an explicit or implicit pager.<cmd> = false setting. Thus it turns the pager on if output is going to a terminal rather than unconditionally.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> --- Noticed while testing. (It might be nice to have an --always-paginate facility to allow debugging by writing output from a pager into something that is not a terminal.)
Documentation/git.txt | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt index 01c4631..f26641a 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -229,7 +229,10 @@ help ...`. -p:: --paginate:: - Pipe all output into 'less' (or if set, $PAGER). + Pipe all output into 'less' (or if set, $PAGER) if standard + output is a terminal. This overrides the `pager.<cmd>` + configuration options (see the "Configuration Mechanism" section + below). --no-pager:: Do not pipe git output into a pager. @@ -401,7 +404,8 @@ people. Here is an example: ------------ Various commands read from the configuration file and adjust -their operation accordingly. +their operation accordingly. See linkgit:git-config[1] for a +list. Identifier Terminology
-- 1.7.0