X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=r+fmyE5okDRkDuK2cuDXLzKH7eJ1EQ5Czj2B5kISXwnkpnrDw1eYs
	ivnKgdbtV7jfjFqa2b9QucohqfsTTYYXb0UNnpMwDiK0nRG7MJ/1SDgGU76ELDlx
	+lNruy6QL9KVc2xwVt4ErdawRYYWNQYvaF0mMBoW1qLd6PHDozAOL8=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=9VmD+AZfgdQ6Aw/TZsRCqDf4n58=; b=FqYyi2LeLRGLUblUPHr1WF6cziBY
	gL1L2hqTMfKPd0ho+rFrqTCPKw7O58KS75b5pV9BFwZ/q+RNKVF0yMoyB57cH+lT
	Ysf/gg9fB0tsuPcSOm5LHD+yaRydxAFe/hhHiZvKMVLaQP2eqQV2Dr4LdNygwOnS
	YGYSxEvUIbKcb1U=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=1.6 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RDNS_NONE autolearn=no version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1/P83pibOrbWaffZpKGL2NF
Date:	Fri, 26 Jul 2013 01:49:06 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: BLODA extension: console interoperability
Message-ID:	<20130726054906.GC477@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
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>
MIME-Version:	1.0
In-Reply-To:	<CAHWeT-bBvWyv0dzFkwbgyKJKuNyaVY85ZBkksCC-Qs_dZ6H+GA@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

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

- Raw text -