[PATCH] Documentation: clarify pager.<cmd> configuration
- From
Jonathan Nieder <jrnieder@uchicago.edu>
- Date
- Aug 24, 2008, 05:38 UTC
- Message-ID
- <Pine.GSO.4.62.0808240028450.28567@harper.uchicago.edu>
- In-Reply-To
- <Pine.GSO.4.62.0808240019050.28567@harper.uchicago.edu>
It was not obvious from the text that pager.<cmd> is a boolean setting.
While we're changing the description, make some other improvements: lest we forget and fret, clarify that -p and pager.<cmd> do not kick in when stdout is not a tty; point to related core.pager and GIT_PAGER settings; use renamed --paginate option.
Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu> --- This is not related to the core.pager documentation patch I just sent; it just caught my eye as I was reading over the file.
Documentation/config.txt | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt index 88638f7..b12e695 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -988,9 +988,11 @@ pack.packSizeLimit:: linkgit:git-repack[1]. pager.<cmd>:: - Allows to set your own pager preferences for each command, overriding - the default. If `\--pager` or `\--no-pager` is specified on the command - line, it takes precedence over this option. + Allows turning on or off pagination of the output of a + particular git subcommand when outputing to a tty. If + `\--paginate` or `\--no-pager` is specified on the command line, + it takes precedence over this option. To disable pagination for + all commands, set `core.pager` or 'GIT_PAGER' to "`cat`". pull.octopus:: The default merge strategy to use when pulling multiple branches
-- 1.6.0.481.g9ef3