From: Jeff King <peff@peff.net>
Date: Mon, 23 Jun 2008 15:23:10 GMT
Subject: Re: about c8af1de9 (git status uses pager)
Message-ID: <20080623152309.GA24101@sigill.intra.peff.net>
In-Reply-To: <7vtzfln5zw.fsf@gitster.siamese.dyndns.org>

On Sun, Jun 22, 2008 at 03:01:07AM -0700, Junio C Hamano wrote:

> Jeff had a patch to allow boolean configuration variable "pager.<command>"
> to override the built-in pager settings during 1.5.6 cycle, and I think it
> was a reasonable approach to take.  People who want to page output from
> git-status can then set "pager.status = true" in their configuration (and
> then we can revert c8af1de (make git-status use a pager, 2008-04-23)).
> Alternatively we could keep the current status-quo for the default, and
> people can say "pager.status = false" in their configuration.

I have been running with the patch for a month or two, and it works fine
for controlling the pager. Unfortunately, there is a nasty interaction
in the git wrapper with reading the config file early, and we end up not
calculating the GIT_DIR and worktree in the same way. I think this is
part of a larger problem which needs solving, but everytime I look at
it, my eyes start bleeding (and I have to admit, since the patch does
work, I have forgotten how annoyed I was at the paging behavior in the
first place, and I don't have as much motivation to work on it).

I think this is deeply related to the "git config alias.st status && cd
.git && git st" problem, which is also on my long-term todo. So I'll see
if I can do something about it during this release cycle.

-Peff