git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Dario Rodriguez <soft.d4rio@gmail.com>
Cc: Jeff King <peff@peff.net>,
	Ben Walton <bwalton@artsci.utoronto.ca>,
	git <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] Fix for default pager
Date: Tue, 08 Jun 2010 16:17:39 +0200	[thread overview]
Message-ID: <4C0E5103.7030501@viscovery.net> (raw)
In-Reply-To: <AANLkTilvvpy4TBQF6g8boQL87FRB7kFDrVfYiHvOv6xu@mail.gmail.com>

Am 6/8/2010 15:49, schrieb Dario Rodriguez:
> we must correct
> something... the other way is that if pager fails to execute, we
> cannot simply return 0.

But we do not return 0:

 $ GIT_PAGER=/is/not/there git log
 $ echo $?
 141

That's SIGPIPE, just as I would expect.

And with this change

diff --git a/pager.c b/pager.c
index dac358f..86519cc 100644
--- a/pager.c
+++ b/pager.c
@@ -89,9 +89,6 @@ void setup_pager(void)
 		static const char *env[] = { "LESS=FRSX", NULL };
 		pager_process.env = env;
 	}
-#ifndef WIN32
-	pager_process.preexec_cb = pager_preexec;
-#endif
 	if (start_command(&pager_process))
 	return;


I get:

 $ GIT_PAGER=/is/not/there ./git log -1 --oneline
 error: cannot run /is/not/there: No such file or directory
 1a16cee merge-recursive: demonstrate an incorrect conflict with submodule

-- Hannes

  reply	other threads:[~2010-06-08 14:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Installing on AIX fails>
2010-06-07 23:58 ` [PATCH/RFC] Fix for default pager Dario Rodriguez
2010-06-08  0:04   ` Ben Walton
2010-06-08  2:14     ` Dario Rodriguez
2010-06-08  5:35       ` Jeff King
2010-06-08 13:49         ` Dario Rodriguez
2010-06-08 14:17           ` Johannes Sixt [this message]
2010-06-08 14:39             ` Dario Rodriguez
2010-06-08 15:56               ` Johannes Sixt
2010-06-08 17:28                 ` Dario Rodriguez
2010-06-08 18:59                   ` Johannes Sixt
2010-06-08 20:44                     ` Dario Rodriguez
2010-06-08 21:33                       ` Andreas Ericsson
2010-06-09  9:08                         ` Tor Arntsen
2010-06-09  9:29                           ` Miles Bader
2010-06-10  8:29                           ` Jeff King
2010-06-10  8:48                             ` Tor Arntsen
2010-06-10  8:59                               ` Jeff King
2010-06-10  9:24                                 ` Tor Arntsen
2010-06-10 11:31                                   ` Dario Rodriguez
2010-06-10 14:55                                 ` Junio C Hamano
2010-06-15 16:11                                 ` Brandon Casey
2010-06-15 16:32                                   ` Tor Arntsen
2010-06-16  1:34                                   ` Nazri Ramliy
2010-06-16  6:28                                   ` Jeff King
2010-06-09 18:57                         ` Ævar Arnfjörð Bjarmason
2010-06-08  5:29   ` Jeff King
2010-06-08  6:12     ` Johannes Sixt
2010-06-08 12:24     ` Dario Rodriguez
2010-06-08 14:04       ` Erik Faye-Lund

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=4C0E5103.7030501@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=bwalton@artsci.utoronto.ca \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=soft.d4rio@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 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).