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=v+1YIxbmPkWNXmLd32JOPph/QpQERaKPbNAPjlyx94zhDDT3kNxdR
	ajN1MSmDXXrvSE/3xH7YVuyuWcdLZOPaXmhlW1ld1k0Ut0PbQBEs3vaafskPFlsG
	6345ojP0YhubcagpMdQdZWDoAzEo1VV8cTbJrDfy/jbbyfbdbLKWFY=
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=bLTzVNkvoywxqJkSjOUtn0RkTfI=; b=uS316yzfDBa3Gq958eOiI3wudYVF
	9NsZi5bDsbvbRr2CCRn4o2aL3/PKavGv1p2hErBPNKDQxJyPAnq3OU6dV0LGgJgt
	c5qBYhnZn7R59Nzbj2u7wh7j1TxGfvA4UtH6bwCwYZst0y+CvEjzpNn8pkpX7kyo
	zvnw8UdauVFlpU0=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-5.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SEMBACKSCATTER autolearn=no version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
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+8GLjFViFhwtqKQSuF2jHC
Date: Fri, 2 May 2014 01:33:30 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Screen crippled by applications using alternative screen
Message-ID: <20140502053330.GA3882@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <loom DOT 20140425T174944-109 AT post DOT gmane DOT org> <20140425173617 DOT GB346 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20140501T121117-28 AT post DOT gmane DOT org> <5362C651 DOT 9090402 AT cygwin DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5362C651.9090402@cygwin.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, May 01, 2014 at 06:10:25PM -0400, Larry Hall (Cygwin) wrote:
>On 05/01/2014 06:13 AM, Maximus5 wrote:
>> Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:
>>
>>> I don't see the behavior that you are specifying but I doubt that what
>>> you are seeing has anything to do with the gobbledegook on the above
>>> page.  If you do want "Cygwin" to send ANSI escape sequences then you'll
>>> need to make sure that you're using a package which knows how to send
>>> them, i.e., an ncurses-using package, and that the TERM environment
>>> variable is set appropriately.
>>
>> Hi, about gobbledegook
>>
>> Looking into imports of cygwin's shot.exe I can see "cygncursesw-10.dll".
>>
>> Does that mean it is "using a package which knows how to send them"?
>>
>> Checking for environment
>> $ set | grep TERM
>> TERM=xterm
>>
>> Ok?
>>
>> But sh.exe is using Windows console API instead of writing ANSI to stdout.
>>
>> What is wrong?
>
>If you're using the Windows console (cmd.exe, Console2, ConEmu, etc.), then
>you're not going to get complete ANSI code support regardless of what you
>set your TERM environment variable to.  If you're saying that you're using
>mintty or xterm and having problems, then you need to provide a clear recipe
>to reproduce the problem so that someone here can try to reproduce it.  For
>more details on what's needed, please see the problem reporting guidelines
>found at the link below:
>
><http://cygwin.com/problems.html>

I think I understand now.  The request if for Cygwin to "do nothing"
when it sees escape sequences since, apparently, ConEmu will handle
escape sequences on its own.  This is not a bug in Cygwin but, a request
for different functionality.  And, on rereading, the web page, I see
that I just wasn't getting what was being requested.  That was because I
was thinking about this from the point of view of someone reporting this
as an apparent long-standing bug in Cygwin when it was nothing of the
sort.

Anyway, gobbledegook label withdrawn.  Sorry.

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