8:58 p.m.
Hi,
I noticed that when I ssh into a CentOS 7 Host I get slightly darker
colors in the ls output compared to the local (gnome-terminal) bash.
Since I'm using a dark background the darker blue used for directories
for example on the remote host is harder to read then the slightly
brighter blue used on the local system.
Does anyone have an idea why the colors are different and how to change
that?
Regards,
Dennis
9:18 p.m.
On 01/28/16 10:58, Dennis Jacobfeuerborn wrote:
Hi,
I noticed that when I ssh into a CentOS 7 Host I get slightly darker
colors in the ls output compared to the local (gnome-terminal) bash.
Since I'm using a dark background the darker blue used for directories
for example on the remote host is harder to read then the slightly
brighter blue used on the local system.
Does anyone have an idea why the colors are different and how to change
that?
You should have an environment variable of LS_COLORS. Check for differences or simply
take the settings from the system you prefer and set it in the other system. Normally,
you'd put that in your .bashrc if your using bash as your shell.
--
In reality, some people should stick to running Windows and others should stay away from
computers altogether.
9:45 p.m.
On 01/27/2016 06:58 PM, Dennis Jacobfeuerborn wrote:
Hi,
I noticed that when I ssh into a CentOS 7 Host I get slightly darker
colors in the ls output compared to the local (gnome-terminal) bash.
Since I'm using a dark background the darker blue used for directories
for example on the remote host is harder to read then the slightly
brighter blue used on the local system.
Does anyone have an idea why the colors are different and how to change
that?
Type "env" to see your environment variables: one of them is LS_COLORS.
I'm guessing they are different on the two machines.
5:48 a.m.
On Thu, 2016-01-28 at 03:58 +0100, Dennis Jacobfeuerborn wrote:
I noticed that when I ssh into a CentOS 7 Host I get slightly darker
colors in the ls output compared to the local (gnome-terminal) bash.
Since I'm using a dark background the darker blue used for directories
for example on the remote host is harder to read then the slightly
brighter blue used on the local system.
Does anyone have an idea why the colors are different and how to
change that?
Two approaches:
You have environment variables which say what colour codes to use with
which filetypes. It would seem one system is merely using blue, the
other using bright and blue (it's a two-part thing).
Depending on what your terminal is, if you're using a graphical one, you
can change the palette used by each colour, and make your dark blue
brighter.
--
tim@localhost ~]$ uname -rsvp
Linux 3.19.8-100.fc20.i686 #1 SMP Tue May 12 17:42:35 UTC 2015 i686
All mail to my mailbox is automatically deleted, there is no point trying
to privately email me, I will only read messages posted to the public lists.
George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.
7:04 a.m.
On 28.01.2016 12:48, Tim wrote:
On Thu, 2016-01-28 at 03:58 +0100, Dennis Jacobfeuerborn wrote:
> I noticed that when I ssh into a CentOS 7 Host I get slightly darker
> colors in the ls output compared to the local (gnome-terminal) bash.
> Since I'm using a dark background the darker blue used for directories
> for example on the remote host is harder to read then the slightly
> brighter blue used on the local system.
> Does anyone have an idea why the colors are different and how to
> change that?
Two approaches:
You have environment variables which say what colour codes to use with
which filetypes. It would seem one system is merely using blue, the
other using bright and blue (it's a two-part thing).
Depending on what your terminal is, if you're using a graphical one, you
can change the palette used by each colour, and make your dark blue
brighter.
Thanks for the pointers everyone. There seems to be a subtle difference
in what "dircolors" reports and what is present in the LS_COLORS env
variable:
0 dennis@nexus ~ $ dircolors
LS_COLORS='rs=0:di=01;34:ln=01;36:mh=00:.....
0 dennis@nexus ~ $ env|grep LS_COLORS
LS_COLORS=rs=0:di=38;5;33:ln=38;5;51:mh=00:.....
Notice how the entries in the dircolors" output have only two values but
the entries in the env variable three values associated with them.
Now I only need to figure out what exactly "di=01;34" vs.
"di=38;5;33"
means...
Regards,
Dennis
11:48 a.m.
On 01/29/2016 05:04 AM, Dennis Jacobfeuerborn wrote:
On 28.01.2016 12:48, Tim wrote:
> On Thu, 2016-01-28 at 03:58 +0100, Dennis Jacobfeuerborn wrote:
>> I noticed that when I ssh into a CentOS 7 Host I get slightly darker
>> colors in the ls output compared to the local (gnome-terminal) bash.
>> Since I'm using a dark background the darker blue used for directories
>> for example on the remote host is harder to read then the slightly
>> brighter blue used on the local system.
>> Does anyone have an idea why the colors are different and how to
>> change that?
> Two approaches:
>
> You have environment variables which say what colour codes to use with
> which filetypes. It would seem one system is merely using blue, the
> other using bright and blue (it's a two-part thing).
>
> Depending on what your terminal is, if you're using a graphical one, you
> can change the palette used by each colour, and make your dark blue
> brighter.
>
Thanks for the pointers everyone. There seems to be a subtle difference
in what "dircolors" reports and what is present in the LS_COLORS env
variable:
0 dennis@nexus ~ $ dircolors
LS_COLORS='rs=0:di=01;34:ln=01;36:mh=00:.....
0 dennis@nexus ~ $ env|grep LS_COLORS
LS_COLORS=rs=0:di=38;5;33:ln=38;5;51:mh=00:.....
Notice how the entries in the dircolors" output have only two values but
the entries in the env variable three values associated with them.
Now I only need to figure out what exactly "di=01;34" vs.
"di=38;5;33"
means...
Regards,
Dennis
This site may help sort out the coding used in LS_COLORS
http://askubuntu.com/questions/466198/how-do-i-change-the-color-for-direc...
/--
~~R/
9:45 p.m.
Allegedly, on or about 29 January 2016, Dennis Jacobfeuerborn sent:
Now I only need to figure out what exactly "di=01;34" vs.
"di=38;5;33"
means...
di = directories to be coloured thus
01 = bold or bright (depends on the terminal which one it does)
34 = blue
If the third one is a set of ANSI colour codes, then I'd say:
38 = an extra colour beyond the defaults, so you probably have something
else that defines what that colour is
5 = flashing text
33 = brown (i.e. dark yellow), possibly this is a fallback option if the
other colour doesn't work
Alternatively, is it a set of RGB colour codes? Like this:
38 = 38/256 of red
5 = 5/256 of green
22 = 33/256 of blue
But only an educated guess.
(I wrote fractions, as it's probably a red level of 38 out of a range of
0 to 255, darkest to brightest, respectively.)
--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
Boilerplate: All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.
If you don't understand how e-mail threading works, then follow the
instructions given by those who do, and don't argue with them.
9:51 p.m.
Allegedly, on or about 29 January 2016, Dennis Jacobfeuerborn sent:
Now I only need to figure out what exactly "di=01;34" vs.
"di=38;5;33"
means...
Ah, now found a reference for the latter
38;5;33
The 38 prefix apparently means to set the foreground colour,
but a 48 prefix apparently means to set the background colour.
No idea how they're using the 5.
The 33 is a colour, but I don't know how that's defined.
Apparently, it's to do with xterm, so you might look into that.
--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
Boilerplate: All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.
Linux servers are always being dæmonised...
12:40 a.m.
On Sun, Jan 31, 2016 at 02:21:04PM +1030, Tim wrote:
Allegedly, on or about 29 January 2016, Dennis Jacobfeuerborn sent:
> Now I only need to figure out what exactly "di=01;34" vs.
"di=38;5;33"
> means...
Ah, now found a reference for the latter
38;5;33
The 38 prefix apparently means to set the foreground colour,
but a 48 prefix apparently means to set the background colour.
No idea how they're using the 5.
The 33 is a colour, but I don't know how that's defined.
Apparently, it's to do with xterm, so you might look into that.
The "3" of 38 is setaf, the 8 is the first part of the color
specification. This 3 number combo is used only on terminals
capable of more than the standard 8, typically 256 colors.
I think the "5" seems to be constant, perhaps meaning a color
beyond the std 8 and the 33 completes the color specification.
jl
--
Jon H. LaBadie jonfu(a)jgcomp.com
6:59 a.m.
On 31.01.2016 07:40, Jon LaBadie wrote:
On Sun, Jan 31, 2016 at 02:21:04PM +1030, Tim wrote:
> Allegedly, on or about 29 January 2016, Dennis Jacobfeuerborn sent:
>> Now I only need to figure out what exactly "di=01;34" vs.
"di=38;5;33"
>> means...
>
> Ah, now found a reference for the latter
>
> 38;5;33
>
> The 38 prefix apparently means to set the foreground colour,
> but a 48 prefix apparently means to set the background colour.
>
> No idea how they're using the 5.
>
> The 33 is a colour, but I don't know how that's defined.
>
> Apparently, it's to do with xterm, so you might look into that.
>
The "3" of 38 is setaf, the 8 is the first part of the color
specification. This 3 number combo is used only on terminals
capable of more than the standard 8, typically 256 colors.
I think the "5" seems to be constant, perhaps meaning a color
beyond the std 8 and the 33 completes the color specification.
I found two good references one for the codes themselves and one for all
the color codes:
https://en.wikipedia.org/wiki/ANSI_escape_code
http://misc.flogisoft.com/bash/tip_colors_and_formatting
38 sets the extended foreground color which can be followed by either:
5:n where n is the color index in a standard 256 color palette or
2;r;g;b to set rgb colors from a 24 bit palette.
Regards,
Dennis
3:08 p.m.
On Sun, Jan 31, 2016 at 01:59:58PM +0100, Dennis Jacobfeuerborn wrote:
On 31.01.2016 07:40, Jon LaBadie wrote:
> On Sun, Jan 31, 2016 at 02:21:04PM +1030, Tim wrote:
>> Allegedly, on or about 29 January 2016, Dennis Jacobfeuerborn sent:
>>> Now I only need to figure out what exactly "di=01;34" vs.
"di=38;5;33"
>>> means...
...
>
> The "3" of 38 is setaf, the 8 is the first part of the color
> specification. This 3 number combo is used only on terminals
> capable of more than the standard 8, typically 256 colors.
>
> I think the "5" seems to be constant, perhaps meaning a color
> beyond the std 8 and the 33 completes the color specification.
I found two good references one for the codes themselves and one for all
the color codes:
https://en.wikipedia.org/wiki/ANSI_escape_code
http://misc.flogisoft.com/bash/tip_colors_and_formatting
38 sets the extended foreground color which can be followed by either:
5:n where n is the color index in a standard 256 color palette or
2;r;g;b to set rgb colors from a 24 bit palette.
Regards,
Dennis
Thanks for correcting my guesswork.
Jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
2:31 p.m.
Try:
cp /etc/DIR_COLORS ~/.dir_colors
edit ~/.dir_colors and make your changes.
implement changes:
eval `dircolors -b ~/.dir_colors`
test your changes:
ls -l
Here's the changes I found most useful for green text on black background:
RESET 0 # reset to "normal" color
DIR 01;37 # directory
LINK 04;36 # symbolic link (If you set this to 'target' instead of a
# numerical value, the color is as for the file pointed to.)
MULTIHARDLINK 00 # regular file with more than one link
FIFO 40;33 # pipe
SOCK 01;35 # socket
DOOR 01;35 # door
BLK 40;33;01 # block device driver
CHR 40;33;01 # character device driver
ORPHAN 40;31;01 # symlink to nonexistent file, or non-stat'able file
MISSING 01;05;37;41 # ... and the files they point to
SETUID 37;41 # file that is setuid (u+s)
SETGID 30;43 # file that is setgid (g+s)
CAPABILITY 30;41 # file with capability
STICKY_OTHER_WRITABLE 30;42 # dir that is sticky and other-writable (+t,o+w)
OTHER_WRITABLE 34;42 # dir that is other-writable (o+w) and not sticky
STICKY 37;44 # dir with the sticky bit set (+t) and not other-writable
# This is for files with execute permission:
EXEC 01;32
Links are underlined which is nice.
Bill
On 1/27/2016 9:58 PM, Dennis Jacobfeuerborn wrote:
Hi,
I noticed that when I ssh into a CentOS 7 Host I get slightly darker
colors in the ls output compared to the local (gnome-terminal) bash.
Since I'm using a dark background the darker blue used for directories
for example on the remote host is harder to read then the slightly
brighter blue used on the local system.
Does anyone have an idea why the colors are different and how to change
that?
Regards,
Dennis
3017
days inactive
3020
days old
11 comments
7 participants
participants (7)
-
Bill Shirley -
Dennis Jacobfeuerborn -
Ed Greshko -
Jon LaBadie -
Mike Wright -
Richard England -
Tim