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:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=sA7AVFT1qeOV3Sq8
	TAKtyRI1ty6O0PVHDQR7qorCQE2LTvxSDevHhRhW+219NhYb5xd0CZ8jD+Dpa9bo
	klWc/HMogQqe0gwYUPWaRPOGcbPI/sKp2IJ3JuGtDmlzjibj2+Rk7tzrpNiUAsjA
	HeTwKg/x5tM114r5wQnTTz10z7E=
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:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=CC2p72N84lDRahdkYBTYAY
	g7aXg=; b=dCzd7CmqNNqvfa7GNdUzD3+m5YhK2iD9+RwipmLKC4XwVpwFTP7m3z
	kaCQjuA2ZDLrWtp2ph6FbDBDm6/y5EnHBVyEAgooIF73ezeeSrkXnwikNh/HYHKz
	VHQjN3iru539wXGYV/tjjZ+8V0HkCHFvylI1wrsNvDPT73bycDrB8=
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-Spam-SWARE-Status: No, score=-5.8 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=Escape
X-HELO: smtp-out-no.shaw.ca
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Is Cygwin 3.1.X Stable Enough to Use?
To: cygwin AT cygwin DOT com
References: <817yBTNxU4176Set DOT 1582206646 AT web03 DOT cms DOT usa DOT net> <1613327751 DOT 20200220213642 AT yandex DOT ru> <CAD8GWsuRiKMsDNFJVAT=48uRA92VbVfxUQxmCm7S-j326it2bQ AT mail DOT gmail DOT com> <20200221092029 DOT da2c51cec466dc8339ee0906 AT nifty DOT ne DOT jp>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <7c3ebfda-6f7f-a22d-cdef-bdba946bbec8@SystematicSw.ab.ca>
Date: Thu, 20 Feb 2020 18:15:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <20200221092029.da2c51cec466dc8339ee0906@nifty.ne.jp>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2020-02-20 17:20, Takashi Yano wrote:
> On Thu, 20 Feb 2020 16:28:26 -0500
> Lee wrote:
>> For whatever it's worth, the only problem I've noticed with 3.1.4 was
>> ansi control character handling and that was fixed by importing this
>> bit into the registry:
>>
>> -------------
>> Windows Registry Editor Version 5.00
>>
>> [HKEY_CURRENT_USER\Console]
>> "VirtualTerminalLevel"=dword:00000001
>> -------------
> 
> In what situation is registry modification obove necessary?

Enables Console Host Virtual Terminal ANSI Escape Sequence Support; see:
https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences
https://docs.microsoft.com/en-us/windows/console/setconsolemode
https://blogs.msdn.microsoft.com/commandline/2017/06/20/understanding-windows-console-host-settings/
https://devblogs.microsoft.com/commandline/new-experimental-console-features/
https://devblogs.microsoft.com/commandline/24-bit-color-in-the-windows-console/
https://devblogs.microsoft.com/commandline/windows-command-line-unicode-and-utf-8-output-text-buffer/
https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/
https://devblogs.microsoft.com/commandline/windows-command-line-inside-the-windows-console/
https://devblogs.microsoft.com/commandline/windows-command-line-the-evolution-of-the-windows-command-line/
https://devblogs.microsoft.com/commandline/windows-command-line-backgrounder/
https://github.com/MicrosoftDocs/Console-Docs
https://github.com/microsoft/terminal

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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