DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=V7Tfch2
	CDYo1vQ+BotkyKxVq3msMBnHtw8OKNIBLpwtFxDhqwd8MTGh9W+HuC8Th97RLjuA
	j5MfHFLPmhcLEnIljyhsp1Z+ROWH8YcTpTLwJr5uzjG2+2FVnnpMFq5fgBArzfui
	jYmbwlVHlrhUNSmP11nNgIjso096coc/agGM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <0cc4ea70-e1b3-ddb6-419c-82808c1e7f9a@SystematicSw.ab.ca>
References: <817yBTNxU4176Set.1582206646@web03.cms.usa.net> <1613327751.20200220213642@yandex.ru> <CAD8GWsuRiKMsDNFJVAT=48uRA92VbVfxUQxmCm7S-j326it2bQ@mail.gmail.com> <20200221092029.da2c51cec466dc8339ee0906@nifty.ne.jp> <7c3ebfda-6f7f-a22d-cdef-bdba946bbec8@SystematicSw.ab.ca> <20200221102722.f7832096e9461b5d5dc8e7c4@nifty.ne.jp> <0cc4ea70-e1b3-ddb6-419c-82808c1e7f9a@SystematicSw.ab.ca>
From: Lee <ler762@gmail.com>
Date: Thu, 20 Feb 2020 21:00:29 -0500
Message-ID: <CAD8GWssi_yCv9-18VPjzeR9sH-39Lu0z=GpQV2EaDuokBYSTtA@mail.gmail.com>
Subject: Re: Is Cygwin 3.1.X Stable Enough to Use?
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On 2/20/20, Brian Inglis  wrote:
> On 2020-02-20 18:27, Takashi Yano wrote:
>> On Thu, 20 Feb 2020 18:15:59 -0700
>> Brian Inglis wrote:
>>> 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
>>
>> I mean what is the problem which need this in cygwin.
>
> Windows programs which emit (or use?) console ANSI escape sequences run from
> cmd

This was from a mintty console(?) session.  There shouldn't have been
any windows programs involved.

Regards,
Lee

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