From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: BLODA extension: console interoperability
Date: Fri, 26 Jul 2013 06:44:00 -0000 [thread overview]
Message-ID: <20130726054906.GC477@ednor.casa.cgf.cx> (raw)
In-Reply-To: <CAHWeT-bBvWyv0dzFkwbgyKJKuNyaVY85ZBkksCC-Qs_dZ6H+GA@mail.gmail.com>
On Fri, Jul 26, 2013 at 05:44:02AM +0100, Andy Koppe wrote:
>On 26 July 2013 05:14, Warren Young wrote:
>> On 7/25/2013 17:06, Larry Hall (Cygwin) wrote:
>>>
>>> I might personally prefer to describe and list them differently.
>>
>>
>> DONOPWOL:
>>
>> DOes
>> NOt
>> Play
>> Well with
>> Others
>> List
>
>I don't think that's fair, since such apps were designed for the
>Windows console, without being aware of Cygwin's pipe-based ptys. And
>unfortunately that list would be very long anyway: basically anything
>interactive that hasn't been explicitly adapted to Cygwin ptys, for
>example by disabling buffering and not relying on the console's
>history facility.
>
>Speaking of which: somebody on the mintty mailing list would like to
>make a Windows program Cygwin-aware by detecting whether it's running
>in a Cygwin terminal (as opposed to having its input or output
>redirected to plain pipes). Does anyone know a way to do this?
Why not just always flush stdout if it's opened on a pipe?
cgf
--
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:[~2013-07-26 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 23:07 Warren Young
2013-07-26 2:50 ` Larry Hall (Cygwin)
2013-07-26 4:44 ` Warren Young
2013-07-26 5:02 ` Larry Hall (Cygwin)
2013-07-26 5:20 ` Andy Koppe
2013-07-26 6:13 ` Warren Young
2013-07-26 6:44 ` Christopher Faylor [this message]
2013-07-26 14:59 ` Pavel Fedin
2013-07-26 16:22 ` Christopher Faylor
2013-07-27 3:18 ` Charles Wilson
2013-07-29 9:06 ` Pavel Fedin
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=20130726054906.GC477@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).