git.1: Clarify the behavior of the --paginate option
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> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
64778d24a9
commit
06300d9753
@ -229,7 +229,10 @@ help ...`.
|
|||||||
|
|
||||||
-p::
|
-p::
|
||||||
--paginate::
|
--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::
|
--no-pager::
|
||||||
Do not pipe git output into a 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
|
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
|
Identifier Terminology
|
||||||
|
Loading…
Reference in New Issue
Block a user