public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: Cygwin Mailing List <cygwin@cygwin.com>
Subject: Calling a Windows program changes terminal character attributes
Date: Sun, 16 Feb 2020 07:45:00 -0000	[thread overview]
Message-ID: <f16e4909-6af5-093d-90e0-c40455e42f9e@maxrnd.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

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.

This only affects the currently-visible part of the screen buffer.  If you 
scroll up, older buffer contents are seen to be unchanged.

I am attaching my DIR_COLORS.local file which is appended to the system's 
DIR_COLORS by these commands in my .bashrc:

eval `dircolors -b /etc/DIR_COLORS`
LS_COLORS0=$LS_COLORS
eval `dircolors -b /home/mark/DIR_COLORS.local`
export LS_COLORS="$LS_COLORS0$LS_COLORS"

I'm using a 64-bit Cygwin1.dll built from current git, on Windows 
10.0.18363.592.  I've also aliased: ls='ls -AF --color -b -T 0 '.

..mark

[-- Attachment #2: DIR_COLORS.local --]
[-- Type: text/plain, Size: 678 bytes --]

.c 00;36
.c.safe 01;36
.h 00;36
.h.safe 01;36
.cc 00;36
.cc.safe 01;36
.cpp 00;36
.cpp.safe 01;36
.hpp 00;36
.hpp.safe 01;36

.s 00;36
.bl 00;36
.m4a 00;36
.b 00;36
.m 00;36
.m4 00;36
.go 00;36
.go.safe 01;36
.cal 00;36
.cal.safe 01;36
.calc 00;36
.pl 00;36
.py 00;36
.awk 00;36

*akefile 00;31
*akefile.safe 01;31
*akefile.in 00;31
*akefile.in.safe 01;31
*akefile.am 00;31
*akefile.am.safe 01;31
.mak 00;31
.mak.safe 01;31
.mk 00;31
.mk.safe 01;31
.ac 00;31

.htm 00;33
.html 00;33
.css 00;33
.xml 01;33
.pdf 01;33
.tex 01;33
.txt 01;33
.log 01;33

.o 00;32
.lo 00;32
.a 00;32
.la 00;32
.dll 00;32
.dll.safe 01;32
.lib 00;32
.lib.safe 01;32
.dll.a 00;32
.dbg 00;32

.bin 00;34

[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


--
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-16  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16  7:45 Mark Geisert [this message]
2020-02-16  8:09 ` Takashi Yano
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=f16e4909-6af5-093d-90e0-c40455e42f9e@maxrnd.com \
    --to=mark@maxrnd.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).