public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Is Cygwin 3.1.X Stable Enough to Use?
Date: Fri, 21 Feb 2020 01:49:00 -0000	[thread overview]
Message-ID: <CAD8GWsvOjjSx9t6QQu3QpGT5AJ9LoFkGrwMTiwb+1p8Cvkti7Q@mail.gmail.com> (raw)
In-Reply-To: <20200221092029.da2c51cec466dc8339ee0906@nifty.ne.jp>

On 2/20/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?

see  http://cygwin.com/ml/cygwin/2020-01/msg00217.html

using mintty, started from a desktop shortcut
C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -

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

  parent reply	other threads:[~2020-02-21  1:49 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
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 [this message]
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=CAD8GWsvOjjSx9t6QQu3QpGT5AJ9LoFkGrwMTiwb+1p8Cvkti7Q@mail.gmail.com \
    --to=ler762@gmail.com \
    --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).