From: Jeff King <peff@peff.net>
To: "Jörn Engel" <joern@logfs.org>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: [PATCH] Revert "Stop starting pager recursively"
Date: Sat, 26 Apr 2014 03:13:58 -0400 [thread overview]
Message-ID: <20140426071358.GA7558@sigill.intra.peff.net> (raw)
In-Reply-To: <20140425201048.GB29904@logfs.org>
[+cc Duy, whose patch this is]
On Fri, Apr 25, 2014 at 04:10:49PM -0400, Jörn Engel wrote:
> A second option is to add a --pager (or rather --no-pager) option to
> the command line and allow the user to specify
> GIT_PAGER="git --no-pager -p column --mode='dense color'" git -p branch
I think we have "--no-pager" already. But the "-p" is turning _on_ the
pager, so you could also just omit it. IOW, I really don't understand
why the original command was not simply:
GIT_PAGER="git column --mode='dense color'" git -p branch
The whole infinite loop that the original commit solved is caused by
specifying the "-p". So it sounds like the right solution is "don't do
that". Am I missing something useful that the "-p" does?
I wonder if perhaps the intent was that the user might have set
"pager.column", in which case the use of the pager is implied. I still
think that the right solution is to use "--no-pager" explicitly then. If
the user is invoking git inside GIT_PAGER, it is up to them to save
themselves from infinite recursion.
-Peff
next prev parent reply other threads:[~2014-04-26 7:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 20:46 [PATCH] Revert "Stop starting pager recursively" Jörn Engel
2014-04-25 18:29 ` Jörn Engel
2014-04-25 18:49 ` Matthieu Moy
2014-04-25 20:10 ` Jörn Engel
2014-04-26 7:13 ` Jeff King [this message]
2014-04-26 17:27 ` Junio C Hamano
2014-04-26 17:35 ` Jeff King
2014-04-27 2:12 ` Duy Nguyen
2014-04-27 7:56 ` Jeff King
2014-04-27 15:06 ` Matthieu Moy
[not found] ` <xmqqk3a9s7fm.fsf@gitster.dls.corp.google.com>
2014-04-28 18:32 ` Jörn Engel
2014-04-28 23:04 ` Junio C Hamano
2014-04-28 23:39 ` Jörn Engel
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=20140426071358.GA7558@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=joern@logfs.org \
/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).