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:reply-to:subject:to:references:from:cc
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=nP5Jy4y1q87UunzP
	2GnhI0BpULkVm59/G+mrtUrikeGeorY5bteqWQF8mhpY3IC0xJ87GAar7wxGCzqq
	Jk+AS+t8uwKWbfa2okhpNr+5pH3k68IcrdjgwhvDssCF0rnZr0fchBxYoUeEcqBm
	Fia1aQhibB7FxHVNeQmMz+FAbGE=
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:reply-to:subject:to:references:from:cc
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=WtZVHrvnqQZXWn25qyx5p9
	1ckWg=; b=ibn2kIKNEmETfDQG3yzvUmddM61zseXvZplG3eI/Hd2VuAd/k3bnMd
	j7BZ4wE6Q4gdtBbStLXqK1qaENwKD5zPXU3X3t1fIRLN/GZcrI/K/8NhdBZ2iXtr
	3weyDF2t9wStXUTpLZz82CjdJPhxJmy56yZMjiP1ZPYuuUNM7Dt8E=
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=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=World, hierarchy, H*f:sk:14aba7e, esc
X-HELO:	mail-lf0-f41.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:to:references:from:organization :cc:message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=1+I+oT3a89xGpJKYcvUeJ5svC0ospF/2xBnuo8Nc2Tc=; b=YoYEjrgk8n9QboqWv6xcBye4hCO2OZ6RxxdLm7Li5Qb+S4zv1bzt/xKxS3s/QbgBK8 B09yjMi0g0TCKbUQxH9HQByS5kx3NSNj886rKCGZSoqx/8/t9YdyjCKvFMbEThPhwCPn j+5eup0jKUrTuUjEPE9auxHwCStKiqf1QzGmrgKORRbK/D70m5QPaNsJgRc+b/TYCBtd IFfp6EZRaaNk6KiZ7IeVWz1BYZHcM5S5Bl3RUukoTp99ZLQmTOtKZ+oZgL4wDPriibpW 1yadss9tStaMt7rPaJkc3D9Q9JR91GQH2PQH4fC3Hk20H2xohTO25jCUszH4nL69xDt6 eawg==
X-Gm-Message-State:	AA6/9Rnr/sKQBR3uBij5C1BIKa0BpQkQJrtDtVUEkVZ3a03XHdkDS1jDKUAmxgenwYKyXQ==
X-Received:	by 10.25.75.216 with SMTP id y207mr804284lfa.100.1476273600198; Wed, 12 Oct 2016 05:00:00 -0700 (PDT)
Reply-To:	andrewbass AT gmail DOT com
Subject:	Re: Escape sequences unprocessed under the "cygwin" terminal
To:	cygwin AT cygwin DOT com
References:	<57FDF60B DOT 4000206 AT gmail DOT com> <14aba7e2-a859-5476-f460-5721e3b9e61d AT gmail DOT com>
From:	"Andrey ``Bass'' Shcheglov" <andrewbass AT gmail DOT com>
Cc:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID:	<57FE25BE.80207@gmail.com>
Date:	Wed, 12 Oct 2016 14:59:58 +0300
User-Agent:	Mozilla/5.0 (Windows NT 6.3; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
MIME-Version:	1.0
In-Reply-To:	<14aba7e2-a859-5476-f460-5721e3b9e61d@gmail.com>
X-IsSubscribed:	yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Marco,

Thank you for your response.

On 12.10.2016 13:32, Marco Atzeri wrote:
> On 12/10/2016 10:36, Andrey ``Bass'' Shcheglov wrote:
>>
>> It works fine under regular Unices, and also under xterm and mintty
>> (in Cygwin), but I'm having trouble running it under the "cygwin"
>> terminal (i. e. bash launched from cmd.exe).
> 
> cmd is not a Cygwin terminal, it is a limited Windows one.
> What is the problem to use mintty ?

There's no problem. I'm just trying to understand the limitations of
cmd.exe (TERM=cygwin). FWIK, bash.exe *can* properly translate ANSI
escape sequences into WinAPI calls. Strangely, the same C program:

> #include <stdio.h>
> 
> int main() {
> 	const char esc = 0x1b;
> 	printf("%c[31;91;1mHello, World!%c[0m\n", esc, esc);
> 	return 0;
> }

behaves correctly with TERM=cygwin when compiled with Cygwin GCC and
linked against cygwin1.dll:

> $ ldd test-ansi-escape.exe
> 	ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffeeb450000)
> 	KERNEL32.DLL => /cygdrive/c/Windows/system32/KERNEL32.DLL (0x7ffee92c
0000)
> 	KERNELBASE.dll => /cygdrive/c/Windows/system32/KERNELBASE.dll (0x7ffe
e8700000)
> 	cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000)

and displays garbage like

> ←[31;91;1mHello, World!←[0m

when compiled with MSVC as a native Windows application:

> $ ldd test-ansi-escape.exe
> 	ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffeeb450000)
> 	ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x770a0000)
> 	wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x76fd0000)
> 	wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x77020000
)
> 	wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x77090000
)
> 	??? => ??? (0x1040000)
> 	KERNEL32.DLL => /cygdrive/c/Windows/SYSTEM32/KERNEL32.DLL (0x76480000
)
> 	??? => ??? (0x1040000)
> 	??? => ??? (0x1040000)
> 	KERNEL32.DLL => /cygdrive/c/Windows/SYSTEM32/KERNEL32.DLL (0x76480000
)
> 	KERNELBASE.dll => /cygdrive/c/Windows/SYSTEM32/KERNELBASE.dll (0x74b4
0000)
> 	MSVCR120D.dll => /cygdrive/c/Windows/SYSTEM32/MSVCR120D.dll (0x62b900
00)

>> Also, if I log in to my Windows box using SSH (i. e. replace the loca
l
>> connection with the remote one, but retain the same |"cygwin|"
>> terminal), again, escape sequences are processed just fine.
> 
> from Unix ? The terminal on that side is able to properly manage
> escape sequence

No, from Windows. I mean, I'm doing "ssh.exe localhost" (the process
hierarchy being cmd.exe -> bash.exe -> ssh.exe -> bash.exe) -- and
everything is working again!

> use mintty.
> It is the recommended one for cygwin

I understand mintty is superior feature-wise compared to cmd.exe, and
xterm is superior to both mintty and cmd.exe -- just like I said, I'm
trying to understand the limitations of cmd.exe (TERM=cygwin).

Regards,
Andrey.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlf+Jb4ACgkQFX2weoTrDGcDjQCeLfk7Nxeg/SGHZEEa2sPuhWli
MrsAn3rGf/9tcTPD1iAFjFMJYHGjR2fC
=cCH2
-----END PGP SIGNATURE-----

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