From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: Is Cygwin 3.1.X Stable Enough to Use?
Date: Fri, 21 Feb 2020 01:27:00 -0000 [thread overview]
Message-ID: <20200221102722.f7832096e9461b5d5dc8e7c4@nifty.ne.jp> (raw)
In-Reply-To: <7c3ebfda-6f7f-a22d-cdef-bdba946bbec8@SystematicSw.ab.ca>
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.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
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
next prev parent reply other threads:[~2020-02-21 1:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 13:50 KARL BOTTS
2020-02-20 18:50 ` Andrey Repin
2020-02-20 21:28 ` Lee
2020-02-21 0:20 ` Takashi Yano
2020-02-21 1:16 ` Brian Inglis
2020-02-21 1:27 ` Takashi Yano [this message]
2020-02-21 1:35 ` Brian Inglis
2020-02-21 1:50 ` Takashi Yano
2020-02-21 2:13 ` Lee
2020-02-21 2:01 ` Lee
2020-02-21 1:49 ` Lee
2020-02-21 2:06 ` Takashi Yano
2020-02-21 2:18 ` Lee
2020-02-21 2:47 ` Lee
2020-02-21 9:41 ` Takashi Yano
2020-02-21 11:13 ` Paul Moore
2020-02-21 14:26 ` Lee
2020-02-21 21:34 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200221102722.f7832096e9461b5d5dc8e7c4@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).