git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: Matthieu Moy <matthieu.moy@grenoble-inp.fr>,
	Jeff King <peff@peff.net>, Duy Nguyen <pclouds@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Revert "Stop starting pager recursively"
Date: Mon, 28 Apr 2014 16:04:28 -0700	[thread overview]
Message-ID: <xmqqsioxm4xv.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140428183244.GA6358@logfs.org> ("Jörn Engel"'s message of "Mon, 28 Apr 2014 14:32:44 -0400")

Jörn Engel <joern@logfs.org> writes:

> On Mon, 28 April 2014 10:14:05 -0700, Junio C Hamano wrote:
>> Matthieu Moy <matthieu.moy@grenoble-inp.fr> writes:
>> 
>> > ----- Original Message -----
>> >> On Sun, Apr 27, 2014 at 09:12:39AM +0700, Duy Nguyen wrote:
>> >> 
>> >> > The intent of the commit was "that is a stupid thing to do, but it's
>> >> > not so obvious from the first glance, do not freeze my system for my
>> >> > mistake". But if it stops an actual use case, then I agree it should
>> >> > be reverted.
>> >> 
>> >> Thanks for the explanation. I think we should just go with Jörn's patch
>> >> as-is, then.
>> >
>> > Agreed. At best, the commit message could be improved to explain the
>> > situation, but the patch itself is OK.
>> 
>> True and I agree.
>> 
>> The patch needs sign-off, though (I am looking at $gmane/246644).
>
> Signed-off-by: Joern Engel <joern@logfs.org>
>
> Or do you want me to resend with sob?

Just the Sign-off is trivial enough that even this brainless
patch-monkey^Wpanda should be able to handle.  The part "The log
message could be improved" is something you may be better equipped
to, though.

I'll tentatively queue this; if you or anybody in the thread can
proofread it to typofix it or give me a better phrasing, that would
be very much appreciated.

Thanks.

-- >8 --
From: Jörn Engel <joern@logfs.org>
Date: Mon, 21 Apr 2014 16:46:22 -0400
Subject: [PATCH] pager: do allow spawning pager recursively

This reverts commit 88e8f908f2b0c56f9ccf8134d8ff9f689af9cc84, which
tried to allow

    GIT_PAGER="git -p column --mode='dense color'" git -p branch

and still wanted to avoid "git -p column" to invoke itself.  However,
this falls into "don't do that -p then" category.

In particular, inside "git log", with results going through less, a
potentially interesting commit may be found and from there inside
"less", the user may want to execute "git show <commit>".  Before
the commit being reverted, this used to show the patch in less but
it no longer does.

Signed-off-by: Jörn Engel <joern@logfs.org>
Reviewed-by: Jeff King <peff@peff.net>
Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Acked-by: Duy Nguyen <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 pager.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pager.c b/pager.c
index 0cc75a8..53670a6 100644
--- a/pager.c
+++ b/pager.c
@@ -64,7 +64,7 @@ void setup_pager(void)
 {
 	const char *pager = git_pager(isatty(1));
 
-	if (!pager || pager_in_use())
+	if (!pager)
 		return;
 
 	/*
-- 
2.0.0-rc1-219-gf8dda7a

  reply	other threads:[~2014-04-28 23:04 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
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 [this message]
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=xmqqsioxm4xv.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=joern@logfs.org \
    --cc=matthieu.moy@grenoble-inp.fr \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    /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).