public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Paul Moore <p.f.moore@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Is Cygwin 3.1.X Stable Enough to Use?
Date: Fri, 21 Feb 2020 11:13:00 -0000	[thread overview]
Message-ID: <CACac1F_s4sRTmtTdsjSoHy1mB68=1gWLt0Nw_tVJ4Xs-0UiB8w@mail.gmail.com> (raw)
In-Reply-To: <20200221184114.165a2b601b22bd0a990c9247@nifty.ne.jp>

I had the same issue and it was fixed by 3.1.4, so yes upgrading was
likely the fix.
Paul

On Fri, 21 Feb 2020 at 09:41, Takashi Yano <takashi.yano@nifty.ne.jp> wrote:
>
> On Thu, 20 Feb 2020 21:47:25 -0500
> Lee wrote:
> > On 2/20/20, Lee  wrote:
> > > I'll try backing out the registry change & see if it still happens.
> >
> > It doesn't happen now.
> >
> > I deleted HKEY_CURRENT_USER\Console\VirtualTerminalLevel
> > rebooted
> > deleted all the .o files under /source/tidy & rebuilt
> > The output of cmake looks normal
> >
> > I updated cygwin this morning:
> > 2020/02/20 07:49:28 Augmented Transaction List:
> > 2020/02/20 07:49:28    0 install cygwin                 3.1.4-1
> > 2020/02/20 07:49:28    1   erase cygwin                 3.1.2-1
> > 2020/02/20 07:49:28    2 install cygwin-devel           3.1.4-1
> > 2020/02/20 07:49:28    3   erase cygwin-devel           3.1.2-1
> >
> > is it possible that fixed it?
>
> I am not sure. In my environment the problem does not occur
> even with cygwin 3.1.2. Therefore, the cause cannot be identified.
>
> --
> 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
>

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

  reply	other threads:[~2020-02-21 11:13 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
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 [this message]
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='CACac1F_s4sRTmtTdsjSoHy1mB68=1gWLt0Nw_tVJ4Xs-0UiB8w@mail.gmail.com' \
    --to=p.f.moore@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).