From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Calling a Windows program changes terminal character attributes
Date: Mon, 17 Feb 2020 09:54:00 -0000 [thread overview]
Message-ID: <20200217185341.4de0180752a4c0ffd75b6997@nifty.ne.jp> (raw)
In-Reply-To: <CAD8GWsuOo5h9NjqyztZHjTTwnpZ00RUWmw+40XUZ6+GT7DADJQ@mail.gmail.com>
On Sun, 16 Feb 2020 11:51:27 -0500
Lee wrote:
> On 2/16/20, Takashi Yano wrote:
> > On Sun, 16 Feb 2020 01:31:14 -0800
> > Mark Geisert wrote:
> >> Thanks Takashi for your reply. I just wanted to add that setting
> >> CYGWIN=disable_pcon in the environment does not fix this issue.
> >> Please ignore this if that's what's expected.
> >
> > CYGWIN=disable_pcon is needed to be set before launching mintty.
> > That is, the setting should be in user environment in system
> > property in control panel rather than in .bashrc.
>
> Does setting CYGWIN=disable_pcon do the same thing as adding this to
> the registry?
> -------------
> Windows Registry Editor Version 5.00
>
> [HKEY_CURRENT_USER\Console]
> "VirtualTerminalLevel"=dword:00000001
> -------------
No. They are very differnt. VirtualTerminalLevel=1 enables ANSI
escape sequence handling in command prompt even without flag
ENABLE_VIRTUAL_TERMINAL_PROCESSING.
CYGWIN=disable_pcon disables pseudo console support in PTY.
PTY is used in mintty, xterm, sshd, etc, but not in command prompt.
--
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-17 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 9:31 Mark Geisert
2020-02-16 10:53 ` Takashi Yano
2020-02-16 16:51 ` Lee
2020-02-17 9:54 ` Takashi Yano [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-16 7:45 Mark Geisert
2020-02-16 8:09 ` Takashi Yano
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=20200217185341.4de0180752a4c0ffd75b6997@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).