From: jojelino <jojelino@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin passes through null writes to other software when redirecting standard input/output (i.e. piping)
Date: Fri, 27 Apr 2012 15:12:00 -0000 [thread overview]
Message-ID: <jnecv7$ulg$1@dough.gmane.org> (raw)
In-Reply-To: <20120427001718.GA10533@ednor.casa.cgf.cx>
On 2012-04-27 AM 9:17, Christopher Faylor wrote:
> There's no way that Cygwin could know to "skip" a call to WriteFile().
> Cygwin doesn't interpose itself in the middle of a pipe. That would be
> truly disastrous. If it somehow looked at every pipe read/write rather
> than just allowing I/O to flow from one end to the other, the mailing
> list would be even more filled with people complaining that Cygwin is
> slow.
>
Maybe i can measure how much it slowed down after applying the
workaround of unworkable runtime of some non-free software.
--
Regards.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-04-27 15:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 21:19 James Johnston
2012-04-27 0:17 ` Christopher Faylor
2012-04-27 14:26 ` James Johnston
2012-04-27 16:28 ` Christopher Faylor
2012-04-27 15:12 ` jojelino [this message]
2012-04-27 16:28 ` Christopher Faylor
2012-04-27 9:09 ` cygwin
2012-04-27 14:41 ` Christopher Faylor
2012-04-27 14:38 ` Corinna Vinschen
2012-04-27 22:38 ` James Johnston
2012-04-28 0:25 ` Daniel Colascione
2012-04-28 5:27 ` Christopher Faylor
2012-04-28 11:20 ` Daniel Colascione
2012-05-09 19:00 ` Linda Walsh
2012-05-09 19:21 ` James Johnston
2012-05-09 20:12 ` Christopher Faylor
2012-05-10 16:28 ` James Johnston
2012-05-10 16:33 ` Otto Meta
2012-05-10 17:57 ` Earnie Boyd
2012-05-10 18:39 ` Corinna Vinschen
2012-05-11 9:05 ` Andrey Repin
2012-05-11 3:34 ` Daniel Colascione
2012-05-11 5:08 ` Linda Walsh
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='jnecv7$ulg$1@dough.gmane.org' \
--to=jojelino@gmail.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).