All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
	Bart Trojanowski <bart@jukie.net>,
	git@vger.kernel.org, Jeff King <peff@peff.net>,
	Bart Trojanowski <bart@jukie.net>
Subject: Re: about c8af1de9 (git status uses pager)
Date: Sun, 22 Jun 2008 03:01:07 -0700	[thread overview]
Message-ID: <7vtzfln5zw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vtzflolis.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 22 Jun 2008 02:40:27 -0700")

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.

  reply	other threads:[~2008-06-22 10:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-21 21:21 about c8af1de9 (git status uses pager) Jan Engelhardt
2008-06-21 21:30 ` Vegard Nossum
2008-06-21 21:42   ` Junio C Hamano
2008-06-21 21:45     ` Jan Engelhardt
2008-06-22  9:09       ` Jan Engelhardt
2008-06-22  9:40         ` Junio C Hamano
2008-06-22 10:01           ` Junio C Hamano [this message]
2008-06-23 15:23             ` Jeff King
2008-07-03  2:15             ` Tim Stoakes
2008-07-03 11:46               ` Jeff King
2008-07-03 12:11               ` Johannes Schindelin
2008-07-03 13:37                 ` Wincent Colaiuta
2008-07-03 19:08                   ` Jeff King
2008-07-03 20:10                     ` Wincent Colaiuta
2008-06-22  9:49         ` Vegard Nossum
2008-06-21 21:42 ` Johannes Gilger
2008-06-22  7:24   ` Johannes Gilger
2008-06-26  3:53     ` Dan McGee
2008-06-26  6:04       ` Matthieu Moy
2008-06-26 10:17       ` Wincent Colaiuta
2008-06-26 17:51         ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vtzfln5zw.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=bart@jukie.net \
    --cc=git@vger.kernel.org \
    --cc=jengelh@medozas.de \
    --cc=peff@peff.net \
    --cc=vegard.nossum@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.