Skip to content

Commit

Permalink
git.1: Clarify the behavior of the --paginate option
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Jonathan Nieder authored and Junio C Hamano committed Feb 15, 2010
1 parent 64778d2 commit 06300d9
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions Documentation/git.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down

0 comments on commit 06300d9

Please sign in to comment.