public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: R Steiger <rsteiger@ensemblesoft.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: with LS_COLORS customized, ls's color scheme reverts when cd'ing to directories not under HOME
Date: Sun, 19 Jan 2020 01:16:00 -0000	[thread overview]
Message-ID: <SN6PR08MB401482CA129E62400ACE9236B7330@SN6PR08MB4014.namprd08.prod.outlook.com> (raw)

The directory color assignments for dracula, flat-ui, and several other themes render 'ls -l' listings very hard to read (foreground and background are nearby blue-green shades for "d" entries).  FWIW, currently theme is "dracula", but am getting same results for flat-ui, etc.

I've tried various ways to customize colors, even saving LS_COLORS to a ~/.dir_colors" file, tweaking "DIR 01;31" -> DIR 01;35", and adding "eval `dircolors ~/.dir_colors`" on the last line of .bashrc.

Incanting 'ls -l' in ~ yields a perfectly readable listing.  However, as soon as I cd to some directory not under ~, the scheme reverts to the released one.  I've been unable to find any posts describing any such problem, and am wondering if cd might be invoking some subcutaneous hook that could be messing with LS_COLORS in some way (BTW, in any of the color-reverted directories, LS_COLORS shows the updated "di=01;35" binding, not the released one).

Thanks in advance for any advice/workarounds/fixes.

-rjs

--
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-01-19  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19  1:16 R Steiger [this message]
2020-01-19  6:41 ` Lee
2020-01-19  7:00   ` R Steiger

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=SN6PR08MB401482CA129E62400ACE9236B7330@SN6PR08MB4014.namprd08.prod.outlook.com \
    --to=rsteiger@ensemblesoft.net \
    --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).