From: Jeff King <peff@peff.net>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: Per Cederqvist <cederp@opera.com>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 2/2] pager_in_use: make sure output is still going to pager
Date: Mon, 10 Aug 2015 13:24:49 -0400 [thread overview]
Message-ID: <20150810172448.GA20168@sigill.intra.peff.net> (raw)
In-Reply-To: <98d092607588cb5c98e7a2deb2163f94@www.dscho.org>
On Mon, Aug 10, 2015 at 06:38:10PM +0200, Johannes Schindelin wrote:
> > +const char *pipe_id_get(int fd)
> > +{
> > + static struct strbuf id = STRBUF_INIT;
> > + struct stat st;
> > +
> > + if (fstat(fd, &st) < 0 || !S_ISFIFO(st.st_mode))
> > + return NULL;
>
> Just a quick note: it seems that this check is not really working on
> Windows. I tested this by running this test case manually (because TTY
> is not set on Windows):
Yeah, I'm not too surprised. I'm guessing your st_ino for pipes are all
just the same or something. Or maybe S_ISFIFO doesn't pass (we don't
technically need it, I don't think, and could just drop that check).
Anyway, I had planned that we would need to stick a big "#ifdef WINDOWS"
around these two functions.
> I hope to find some time tomorrow to figure out some workaround that
> makes this work on Windows.
Cool. I can't comment on Windows-specific stuff, but I'm happy to review
the rest of it. :)
-Peff
next prev parent reply other threads:[~2015-08-10 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 15:21 "git pull --rebase" fails if pager.pull is true, after producing a colorized diff it cannot apply Per Cederqvist
2015-08-09 23:42 ` Jeff King
2015-08-10 5:19 ` Jeff King
2015-08-10 5:19 ` [PATCH 1/2] pager_in_use: use git_env_bool Jeff King
2015-08-10 5:23 ` [PATCH 2/2] pager_in_use: make sure output is still going to pager Jeff King
2015-08-10 16:38 ` Johannes Schindelin
2015-08-10 17:24 ` Jeff King [this message]
2015-08-11 7:48 ` Per Cederqvist
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=20150810172448.GA20168@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=cederp@opera.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=jrnieder@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).