From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeff King <peff@peff.net>
Cc: Dario Rodriguez <soft.d4rio@gmail.com>,
jrnieder@uchicago.edu, git@vger.kernel.org
Subject: Re: [PATCH/RFC] Fix for default pager
Date: Tue, 08 Jun 2010 08:12:35 +0200 [thread overview]
Message-ID: <4C0DDF53.5090805@viscovery.net> (raw)
In-Reply-To: <20100608052929.GA15156@coredump.intra.peff.net>
Am 6/8/2010 7:29, schrieb Jeff King:
> On Mon, Jun 07, 2010 at 08:58:08PM -0300, Dario Rodriguez wrote:
>> +#ifdef WIN32
>> +{ /* cannot trust the executable bit, peek into the file instead */
>> + char buf[3] = { 0 };
>> + int n;
>> + int fd = open(name, O_RDONLY);
>> + st.st_mode &= ~S_IXUSR;
>> + if (fd >= 0) {
>> + n = read(fd, buf, 2);
>> + if (n == 2)
>> + /* DOS executables start with "MZ" */
>> + if (!strcmp(buf, "#!") || !strcmp(buf, "MZ"))
>> + st.st_mode |= S_IXUSR;
>> + close(fd);
>> + }
>> +}
>> +#endif
>> + return st.st_mode & S_IXUSR;
>> +}
>> +
>> +const char *git_pager(int stdout_is_tty)
>> {
>> + static const char *pager_bins[] =
>> + { "less", "more", NULL };
>> + static const char *common_binary_paths[] =
>> + { "/bin/","/usr/bin/","/usr/local/bin/",NULL };
>
> ...must we really add code with such ugliness as magic PATHs and DOS
> magic numbers?
Yes and no.
Coding DOS magic numbers is bad because you could wrapped a real pager in
a shell script (even on Windows).
These days, start_command() is able to report ENOENT if it cannot run a
program because it does not exist. However, right in the case of
git_pager() this capability is disabled because it sets this magic
preexec_cb that waits for data in the child process before it execs the
real pager.
If we could get rid of preexec_cb, we could make this work much more
pleasantly. pager_preexec waits for data on stdin; Linus added it to work
around a faulty 'less'. Do we still need it?
-- Hannes
next prev parent reply other threads:[~2010-06-08 6:12 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
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 [this message]
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=4C0DDF53.5090805@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=jrnieder@uchicago.edu \
--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).