Beartooth wrote:
On Fri, 03 Jul 2020 12:02:40 -0700, Samuel Sieb wrote:
> On 7/3/20 11:59 AM, Beartooth wrote:
>> That one is the color dnf upgrade uses to list what it proposes to
>> change. (What it reports while making the changes is fine.) At present
>> it shows bright chartreuse on pale blue -- which just fuzzes out.
>
> If the only problem is the one color from dnf, then either disable dnf
> colors or use the information from the last thread to adjust the color
> that's causing the problem.
I found /etc/dnf/DIR_COLORS, /etc/dnf/DIR_COLORS.256color, and
/etc/dnf/DIR_COLORS.lightbgcolor.
I'm pretty sure those are in /etc, not /etc/dnf. If they're
in the latter, can you confirm that and check what package
provides them (rpm -qf /etc/dnf/DIR_COLORS*)? I don't see
anything providing them.
In the first one, I found among much else
# If you use DOS-style suffixes, you may want to uncomment the following:
#.cmd 01;32 # executables (bright green) I changed 32 to 31; removed
both hashmarks; no joy; rebooted; still no joy.
Am I editing the wrong file? That comment about suffixes doesn't
quite sit right, but I didn't see anything else that looked likelier.
Assuming you really meant /etc/DIR_COLORS*, then to be
clear, 1) that will affect ls rather than dnf; and 2) you
_are_ most likely editing the wrong file if you edit
/etc/DIR_COLORS.
The logic for which of the 3 files is used is in
/etc/profile.d/colorls.sh (for bourne-style shells like
bash). Most modern terminal support 256 colors (at least),
so they'll most likely use /etc/DIR_COLORS.256color.
After you edit it, you must source /etc/profile.d/colorls.sh
to pick up the changes.
You can also copy the proper DIR_COLORS* file to your home
dir to avoid having a clean install overwrite your changes
in /etc. The paths which the colorls.sh script uses are:
$HOME/.dir_colors.$TERM
$HOME/.dircolors.$TERM
$HOME/.dir_colors
$HOME/.dircolors
The first one found is used.
--
Todd