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 02:13:00 -0000 [thread overview]
Message-ID: <CAD8GWssG0Tmu5W2+MqpSyWivCOVCUj4x+bWwPZOx4Cr4KJMySg@mail.gmail.com> (raw)
In-Reply-To: <20200221105032.2c07d01980c64b1694bd7aab@nifty.ne.jp>
On 2/20/20, Takashi Yano wrote:
> On Thu, 20 Feb 2020 18:34:59 -0700
> Brian Inglis wrote:
>> Windows programs which emit (or use?) console ANSI escape sequences run
>> from cmd
>> (which by default switches off Virtual Terminal ANSI Escape Sequence
>> handling
>> for programs run from it) and which do not themselves set that console
>> mode (or
>> can not because they were written for earlier Windows which does not
>> support
>> that flag).
>
> I see. Since it appeared in the context of cygwin stability,
> I thought it is a cygwin problem.
It seems to be a cygwin problem; I've never seen anything like that
with cmake before.
& like I said earlier, this was from a mintty session started from a
desktop shortcut
I don't see that problem on my old PC
$ uname -a
CYGWIN_NT-10.0 i3668 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64 Cygwin
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
next prev parent reply other threads:[~2020-02-21 2: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 [this message]
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=CAD8GWssG0Tmu5W2+MqpSyWivCOVCUj4x+bWwPZOx4Cr4KJMySg@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).