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>
Jonathan Nieder committed
Feb 14, 2010 at 06:02 UTC
06300d9753349a83212360445d241d70a46375fa
1 file changed
+6
-2
Documentation/git.txt
+6
-2
@@ -229,7 +229,10 @@ help ...`.
229
230
-p::
231
--paginate::
232
- Pipe all output into 'less' (or if set, $PAGER).
232
+ Pipe all output into 'less' (or if set, $PAGER) if standard
233
+ output is a terminal. This overrides the `pager.<cmd>`
234
+ configuration options (see the "Configuration Mechanism" section
235
+ below).
236
237
--no-pager::
238
Do not pipe git output into a pager.
@@ -401,7 +404,8 @@ people. Here is an example:
404
------------
405
406
Various commands read from the configuration file and adjust
404
-their operation accordingly.
407
+their operation accordingly. See linkgit:git-config[1] for a
408
+list.
409
410
411
Identifier Terminology