[off-list ref] writes:
Is "status" considered a plumbing layer command? Because I have often
wondered why it does not use the pager by default. I pipe it through
less all the time and it's kind of annoying that it works differently
than everything else.
I would be pretty annoyed if git status would page by default.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
On Fri, Aug 31, 2012 at 08:09:34PM +0200, Andreas Schwab wrote:
[off-list ref] writes:
quoted
Is "status" considered a plumbing layer command? Because I have often
wondered why it does not use the pager by default. I pipe it through
less all the time and it's kind of annoying that it works differently
than everything else.
I would be pretty annoyed if git status would page by default.
This one has been debated for a while. People used to complain that it
did not page, and then we turned on the pager, and then people
complained that it did page. I wrote 4e10738 (Allow per-command pager
config, 2008-07-03) to help settle it, and now you can do:
git config pager.status true
if you really want it. As of 9bad723 (allow command-specific pagers in
pager.<cmd>, 2010-11-17), you can even set it to an arbitrary pager for
each git command.
With all those options, it's amazing that we can still have threads
about what should page. :)
-Peff