From: Daniel Colascione <dancol@dancol.org>
To: cygwin@cygwin.com
Subject: Re: automatically using pipe_byte for certain EXE's
Date: Thu, 26 Jul 2012 18:16:00 -0000 [thread overview]
Message-ID: <50118958.3080909@dancol.org> (raw)
In-Reply-To: <CE9C056E12502146A72FD81290379E9A43640586@ENFIRHMBX1.datcon.co.uk>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On 7/26/12 9:34 AM, Adam Dinwoodie wrote:
> Daniel Colascione wrote:
>> I still don't know why anyone wouldn't want to use pipe_byte all the time.
>
> I think that was covered pretty explicitly by cgf in reply to you some time
> ago:
Cygwin still uses message pipes for ptys in pipe_byte mode, so the
first of cgf's reasons doesn't apply. As for the way message pipes
"more closely mimic" Linux pipes: I don't see it. What's the
difference? And does it matter in practice? Can someone give me an
actual example of a problem caused by using byte pipes in the non-pty
case? I'm not aware of any.
Since message pipes cause problems _in practice_ and byte pipes (which
Cygwin lived with for many years) don't seem to cause problems _in
practice_, pipe_byte should go away and pipe_byte behavior should be
used unconditionally.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2012-07-26 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 14:47 Noel Grandin
2012-07-26 15:59 ` Daniel Colascione
2012-07-26 16:37 ` Adam Dinwoodie
2012-07-26 18:16 ` Daniel Colascione [this message]
2012-07-27 10:07 ` Adam Dinwoodie
2012-07-27 14:57 ` James Johnston
2012-07-26 18:25 ` Adam Dinwoodie
2012-07-27 6:36 ` Noel Grandin
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=50118958.3080909@dancol.org \
--to=dancol@dancol.org \
--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).