From: Junio C Hamano <gitster@pobox.com>
Date: Sun, 22 Jun 2008 10:01:07 GMT
Subject: Re: about c8af1de9 (git status uses pager)
Message-ID: <7vtzfln5zw.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <7vtzflolis.fsf@gitster.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

> Jan Engelhardt <jengelh@medozas.de> writes:
>
>> I am aware that this is a less / xterm issue, but I wanted to let
>> you know.
>
> Do you mean "me" by "let you know"?  Well, I have already been aware of
> it, thanks.

Having said all that, I have to say I am regretting to have accepted that
patch to enable pager on status, not because it bothers me personally (it
doesn't primarily because I practically never run git-status because I
consider the command useless and living almost always in Emacs helps), but
because in principle changing anything that existing users are used to is
bad.

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.