Re: (minor concern) git using the pager should not be a default

From: Jeff King <peff@peff.net>
Date: Aug 31, 2012, 21:43 UTC
Message-ID: <20120831214312.GB3008@sigill.intra.peff.net>
In-Reply-To: <m2a9xblyqp.fsf@igel.home>

On Fri, Aug 31, 2012 at 08:09:34PM +0200, Andreas Schwab wrote:

Show 8 quoted lines

> <dag@cray.com> 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.

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