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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=l1q4SJVXFez/M8AZ5u6RNKZx/KVSTRhipQBdVVge43Q
	ym4M1KEIRNB70b9PBt3IkbrROo3GHEzzpEjK0gi0K4WaYd9P2tI8tomDznz2D5rz
	W6CETPJSO8GEMJquignysr3n2n3IURqGZ8DEZ+3/sV1S0aZC6IXK08Su1xsUgiSo
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=+2Pe/9O50JDwTfNcRJtsyoxEC3I=; b=B2X3jDSvH7aPpu00a
	2BuMYK2Jg/auonFP93szM8Uea1EVP+XuOU8ReyS1esxidNjB9ZGY0Q8aOnaxyllO
	XOL/BecHwNvI1d89rodAcf7z2pELmbkDYWrotk8HcNWZCD434aKUJsL77kwhJW3O
	eBtiVdLeYCozji7gYEjefc40y8=
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.1 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,SPF_PASS autolearn=ham version=3.3.1
Message-ID: <51F32DE4.3090108@cwilson.fastmail.fm>
Date: Fri, 26 Jul 2013 22:18:12 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
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> <003601ce89f8$c3845f10$4a8d1d30$%fedin AT samsung DOT com> <20130726152944 DOT GD4495 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20130726152944.GD4495@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 7/26/2013 11:29 AM, Christopher Faylor wrote:
> On Fri, Jul 26, 2013 at 04:07:55PM +0400, Pavel Fedin wrote:
>> 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.

cygwin-ncurses does not do any of the stuff that Pavel described. It 
treats the cygwin terminal just as described by $TERM (which, if 
TERM=cygwin, uses the terminfo definition we've painstakingly created 
over the years) -- and so takes advantage of the "gloss" that cygwin 
places over the plain console.

OTOH, if TERM=xterm, for instance, then it just uses the xterm terminfo.

--
Chuck



--
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