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=Qmp3ekATscUzSwsZNi6/wLnEt3B31UJANIxXxR13wkJ0cOzkpCY43
	ebg+luXgbJ4GTBgP3hLAomJbtkZc4cnPlkRmJDhFOlFG51OKagrjuZTrBCyEyT2H
	Q/5Zu+sHEHlNpTjD+6KEMAoI+ptFRBmoh+qmPzc48sIZzP6jkzrqJY=
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=85XIzRp729wQB3mbY3fmtj3YZB0=; b=hoF3ugTd/Mc4nM3C1OXPatLQ8AQd
	9Y//a2/f5/36TUFpySrnOv07oad7TJTq0/7RysCj72cE3/jHhAPCERmQv9srBAyn
	jKcMa9WK2jiEWSGmF5smNKdQlbueqGhUQ/+LMtpad4bf4ntxQzDiO+0kYyPIa/L/
	b1tIFM6I4qoJBSM=
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=3.2 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,TO_NO_BRKTS_PCNT 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/uUh0LBt+BefHRpsvZiOnT
Date:	Fri, 26 Jul 2013 11:29:44 -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:	<20130726152944.GD4495@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> <003601ce89f8$c3845f10$4a8d1d30$%fedin AT samsung DOT com>
MIME-Version:	1.0
In-Reply-To:	<003601ce89f8$c3845f10$4a8d1d30$%fedin@samsung.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Fri, Jul 26, 2013 at 04:07:55PM +0400, Pavel Fedin wrote:
> Hello!
>
>> 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
>
> Let me also drop my 5 cents into this...
>We should be very careful about this.  At least there is one case where
>difference between Cygwin console and real Windows console plays a key
>role: ncurses.  Normal Windows console is very basic and does not
>understand 90% of control sequences.  As a result, ncurses has been
>extended with 'terminal drivers', which redirect certain control
>functions to OS (Windows in our case) API calls.  Which, of course,
>work only with real Windows console.

The "console" that a Cygwin program sees is not just the raw Windows
console.  Hopefully the Cygwin version of ncurses understands that
Cygwin extends the functionality of the console so that a big subset of
standard control sequences will just work.

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 -