From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Calling a Windows program changes terminal character attributes
Date: Sun, 16 Feb 2020 08:09:00 -0000 [thread overview]
Message-ID: <20200216170916.7e90f4d55ddf45ce84610681@nifty.ne.jp> (raw)
In-Reply-To: <f16e4909-6af5-093d-90e0-c40455e42f9e@maxrnd.com>
On Sat, 15 Feb 2020 23:44:53 -0800
Mark Geisert wrote:
> This may be a duplicate of an already-reported problem. I haven't seen one
> reported quite this way up to now, though.
>
> I'd long ago modified DIR_COLORS to color-code more kinds of files in 'ls'
> displays. I've noticed for a while (weeks?) that some of the chars visible in a
> terminal window are made bold just by launching certain Windows commands. I
> just now stumbled onto a simple test case.
>
> 1) Open a Cygwin Terminal window,
> 2) cd to a directory with lots of different file types,
> 3) issue an 'ls' command
> 4) issue the command "cmd -c version"
>
> You should immediately see that some characters in the visible part of the
> screen buffer have been converted to bold versions. Not all of them, though.
Thanks for the report.
This is the same issue as that of already reported in:
https://cygwin.com/ml/cygwin/2019-12/msg00149.html
https://cygwin.com/ml/cygwin/2020-02/msg00062.html
I am sorry, but it is difficult to fix right now.
Now, poroposals below is under consideration. If this could be realized,
your problem would be solved.
https://cygwin.com/ml/cygwin/2020-02/msg00065.html
https://cygwin.com/ml/cygwin-patches/2020-q1/msg00151.html
--
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-16 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 7:45 Mark Geisert
2020-02-16 8:09 ` Takashi Yano [this message]
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
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=20200216170916.7e90f4d55ddf45ce84610681@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).