From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Sebastian Celis <sebastian@sebastiancelis.com>, git@vger.kernel.org
Subject: Re: 'git svn log' no longer uses the pager
Date: Sun, 14 Feb 2010 05:54:30 -0600 [thread overview]
Message-ID: <20100214115430.GA1849@progeny.tock> (raw)
In-Reply-To: <20100213235156.GA9054@coredump.intra.peff.net>
Jeff King wrote:
> On Sat, Feb 13, 2010 at 03:14:54PM -0600, Sebastian Celis wrote:
>> Ever since upgrading to git 1.6.6.1 I have noticed that 'git svn log'
>> no longer uses the pager. It definitely used to in git 1.6.5.X, but it
>> no longer does.
[...]
> I think it's a bug. It bisects to Jonathan's dec543e (am -i, git-svn:
> use "git var GIT_PAGER", 2009-10-30). But it seems to me that "git var
> GIT_PAGER" is fundamentally broken.
Yikes, you’re right. Sorry about that.
> For git-config's colorbool support we have the caller pass in a
> stdout-is-tty flag. I suspect we would need to do the same thing here.
Thanks for the helpful reference. I think it is simpler for the caller
to disable the pager himself, i.e., something like patches 2, 4, and 5
below:
Jonathan Nieder (6):
Fix 'git var' usage synopsis
Make 'git var GIT_PAGER' always print the configured pager
git.1: Clarify the behavior of the --paginate option
git svn: Fix launching of pager
am: Fix launching of pager
tests: Add tests for automatic use of pager
Documentation/git-var.txt | 2 +-
Documentation/git.txt | 8 ++-
builtin-var.c | 4 +-
cache.h | 2 +-
git-am.sh | 5 +-
git-sh-setup.sh | 16 +++++
git-svn.perl | 9 ++-
pager.c | 6 +-
t/t7006-pager.sh | 163 +++++++++++++++++++++++++++++++++++++++++++++
9 files changed, 200 insertions(+), 15 deletions(-)
create mode 100644 t/t7006-pager.sh
next prev parent reply other threads:[~2010-02-14 11:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 21:14 'git svn log' no longer uses the pager Sebastian Celis
2010-02-13 23:51 ` Jeff King
2010-02-14 11:54 ` Jonathan Nieder [this message]
2010-02-14 11:55 ` [PATCH 1/6] Fix 'git var' usage synopsis Jonathan Nieder
2010-02-15 2:22 ` Junio C Hamano
2010-02-15 2:36 ` [PATCH v2 " Jonathan Nieder
2010-02-15 4:47 ` Jeff King
2010-02-14 11:59 ` [PATCH 2/6] Make 'git var GIT_PAGER' always print the configured pager Jonathan Nieder
2010-02-15 5:00 ` Jeff King
2010-02-15 5:44 ` Jonathan Nieder
2010-02-15 7:57 ` Jeff King
2010-02-14 12:02 ` [PATCH 3/6] git.1: Clarify the behavior of the --paginate option Jonathan Nieder
2010-02-15 4:55 ` Jeff King
2010-02-14 12:06 ` [PATCH 4/6] git svn: Fix launching of pager Jonathan Nieder
2010-02-15 7:58 ` Eric Wong
2010-02-14 12:07 ` [PATCH 5/6] am: " Jonathan Nieder
2010-02-15 2:30 ` Junio C Hamano
2010-02-15 2:59 ` [PATCH v2 " Jonathan Nieder
2010-02-15 3:25 ` [PATCH v3 " Jonathan Nieder
2010-02-15 4:42 ` Jeff King
2010-02-15 5:04 ` [PATCH v4 " Jonathan Nieder
2010-02-15 5:12 ` Jeff King
2010-02-15 20:26 ` Johannes Sixt
2010-02-14 12:13 ` [PATCH 6/6] tests: Add tests for automatic use " Jonathan Nieder
2010-02-15 5:10 ` Jeff King
2010-02-15 5:35 ` [PATCH v2 " Jonathan Nieder
2010-02-15 5:37 ` 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=20100214115430.GA1849@progeny.tock \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sebastian@sebastiancelis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).