This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: BLODA extension: console interoperability
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 26 Jul 2013 01:49:06 -0400
- Subject: Re: BLODA extension: console interoperability
- References: <51F1A863 dot 8060403 at etr-usa dot com> <51F1AF90 dot 3080409 at cygwin dot com> <51F1F7B4 dot 4060202 at etr-usa dot com> <CAHWeT-bBvWyv0dzFkwbgyKJKuNyaVY85ZBkksCC-Qs_dZ6H+GA at mail dot gmail dot com>
- Reply-to: cygwin at cygwin dot 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