From: Sky Diver <skydivergm@gmail.com>
To: cygwin@cygwin.com
Subject: Re: ANSI colors not showing by default
Date: Mon, 22 May 2017 05:45:00 -0000 [thread overview]
Message-ID: <CADWQZEtZ-30MAbWyi_WFRxkVS3THep0nin_w0HAyg4v+-R=ebw@mail.gmail.com> (raw)
In-Reply-To: <dad39c3a-b71e-d78b-cd33-46d2a35ab990@towo.net>
On Sun, May 21, 2017 at 11:49 PM, Thomas Wolff wrote:
> Hi, your symptom description is quite sparse...
>
> Am 21.05.2017 um 22:45 schrieb Sky Diver:
>>
>> Lately I noticed that colors are not showing by default in some
>> situations.
>> The most apparent case is when running composer.
>
> What "composer"?
PHP composer https://getcomposer.org
>> The latest composer version on "Bash on Ubuntu on Windows" console,
>> and even when running it via a mintty shell looks just fine. But from
>> cygwin the output is monochrome.
>
> "From cygwin" could mean (guessing) from a cygwin console window, where your
> TERM setting would be "cygwin".
> That could cause an application to assume no colour support. So it would
> help if you tell us what your settings are.
(*) I thought that cygcheck.out would answer these type of questions.
The default TERM value is 'xterm', even when I rename my home-dir and
launch a shell that creates a fresh one.
>> I would love to understand what's going on.
>> I tried the following:
>> - Change the TERM var to several values
>
> Which values?
TERM=xterm
TERM=xterm-256color
TERM=Cygwin
TERM=cygwin
This one also didn't help:
export CYGWIN=codepage:ansi
--
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:[~2017-05-21 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 20:50 Sky Diver
2017-05-21 21:02 ` Thomas Wolff
2017-05-22 5:45 ` Sky Diver [this message]
2017-05-22 11:19 ` Richard H Lee
2017-05-22 18:09 ` Sky Diver
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='CADWQZEtZ-30MAbWyi_WFRxkVS3THep0nin_w0HAyg4v+-R=ebw@mail.gmail.com' \
--to=skydivergm@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).