How can I change the color of this blue text on my command line?
Clash Royale CLAN TAG#URR8PPP
I know this question has been asked multiple times but I didn't find the answer on those other questions.
Here an Image to illustrate my point:
Can you read the blue line without squinting? No? Me neither.
I am running an ansible playbook in full verbose mode and need to read those logs with a playbook of 50+ tasks.
Can anyone explain how can I change those colors?
Questions I looked at where I didn't figure out a solution:
- Color1
- Color2
- Color3
- Color4
- ...
terminal colors putty
|
show 3 more comments
I know this question has been asked multiple times but I didn't find the answer on those other questions.
Here an Image to illustrate my point:
Can you read the blue line without squinting? No? Me neither.
I am running an ansible playbook in full verbose mode and need to read those logs with a playbook of 50+ tasks.
Can anyone explain how can I change those colors?
Questions I looked at where I didn't figure out a solution:
- Color1
- Color2
- Color3
- Color4
- ...
terminal colors putty
2
blue over the background shall be visible, although in this case is isn't. Do not try to use shell escapes to change the colours. You need to configure theblue color
in your terminal emulator to something more visible.
– grochmal
Jul 11 '16 at 15:24
@grochmal thanks for the input. How can I do that? Is it LS_Colors or with tput or..... ?
– Joze
Jul 11 '16 at 15:30
Which terminal emulator are you using?
– derobert
Jul 11 '16 at 15:32
@derobert Kitty
– Joze
Jul 11 '16 at 15:32
1
halyph.blogspot.com/2013/01/custom-puttykitty-color-scheme.html ... looks like you should have a settings entry to change the colors. (Really probably off-topic here, at least if editing the KiTTY config turns out to be the answer).
– derobert
Jul 11 '16 at 15:35
|
show 3 more comments
I know this question has been asked multiple times but I didn't find the answer on those other questions.
Here an Image to illustrate my point:
Can you read the blue line without squinting? No? Me neither.
I am running an ansible playbook in full verbose mode and need to read those logs with a playbook of 50+ tasks.
Can anyone explain how can I change those colors?
Questions I looked at where I didn't figure out a solution:
- Color1
- Color2
- Color3
- Color4
- ...
terminal colors putty
I know this question has been asked multiple times but I didn't find the answer on those other questions.
Here an Image to illustrate my point:
Can you read the blue line without squinting? No? Me neither.
I am running an ansible playbook in full verbose mode and need to read those logs with a playbook of 50+ tasks.
Can anyone explain how can I change those colors?
Questions I looked at where I didn't figure out a solution:
- Color1
- Color2
- Color3
- Color4
- ...
terminal colors putty
terminal colors putty
edited Apr 13 '17 at 12:36
Community♦
1
1
asked Jul 11 '16 at 15:20
JozeJoze
151115
151115
2
blue over the background shall be visible, although in this case is isn't. Do not try to use shell escapes to change the colours. You need to configure theblue color
in your terminal emulator to something more visible.
– grochmal
Jul 11 '16 at 15:24
@grochmal thanks for the input. How can I do that? Is it LS_Colors or with tput or..... ?
– Joze
Jul 11 '16 at 15:30
Which terminal emulator are you using?
– derobert
Jul 11 '16 at 15:32
@derobert Kitty
– Joze
Jul 11 '16 at 15:32
1
halyph.blogspot.com/2013/01/custom-puttykitty-color-scheme.html ... looks like you should have a settings entry to change the colors. (Really probably off-topic here, at least if editing the KiTTY config turns out to be the answer).
– derobert
Jul 11 '16 at 15:35
|
show 3 more comments
2
blue over the background shall be visible, although in this case is isn't. Do not try to use shell escapes to change the colours. You need to configure theblue color
in your terminal emulator to something more visible.
– grochmal
Jul 11 '16 at 15:24
@grochmal thanks for the input. How can I do that? Is it LS_Colors or with tput or..... ?
– Joze
Jul 11 '16 at 15:30
Which terminal emulator are you using?
– derobert
Jul 11 '16 at 15:32
@derobert Kitty
– Joze
Jul 11 '16 at 15:32
1
halyph.blogspot.com/2013/01/custom-puttykitty-color-scheme.html ... looks like you should have a settings entry to change the colors. (Really probably off-topic here, at least if editing the KiTTY config turns out to be the answer).
– derobert
Jul 11 '16 at 15:35
2
2
blue over the background shall be visible, although in this case is isn't. Do not try to use shell escapes to change the colours. You need to configure the
blue color
in your terminal emulator to something more visible.– grochmal
Jul 11 '16 at 15:24
blue over the background shall be visible, although in this case is isn't. Do not try to use shell escapes to change the colours. You need to configure the
blue color
in your terminal emulator to something more visible.– grochmal
Jul 11 '16 at 15:24
@grochmal thanks for the input. How can I do that? Is it LS_Colors or with tput or..... ?
– Joze
Jul 11 '16 at 15:30
@grochmal thanks for the input. How can I do that? Is it LS_Colors or with tput or..... ?
– Joze
Jul 11 '16 at 15:30
Which terminal emulator are you using?
– derobert
Jul 11 '16 at 15:32
Which terminal emulator are you using?
– derobert
Jul 11 '16 at 15:32
@derobert Kitty
– Joze
Jul 11 '16 at 15:32
@derobert Kitty
– Joze
Jul 11 '16 at 15:32
1
1
halyph.blogspot.com/2013/01/custom-puttykitty-color-scheme.html ... looks like you should have a settings entry to change the colors. (Really probably off-topic here, at least if editing the KiTTY config turns out to be the answer).
– derobert
Jul 11 '16 at 15:35
halyph.blogspot.com/2013/01/custom-puttykitty-color-scheme.html ... looks like you should have a settings entry to change the colors. (Really probably off-topic here, at least if editing the KiTTY config turns out to be the answer).
– derobert
Jul 11 '16 at 15:35
|
show 3 more comments
4 Answers
4
active
oldest
votes
Nope, never have been able to read blue on black (and life is far too short to fiddle with colour customizations in every terminal or console combination I might use) so I disable colors by default. With xterm
, an .Xdefaults
entry of:
XTerm*colorMode:false
does wonders; otherwise, without a means to kill the colors in the terminal, application specific hacks may be necessary; a quick kluge is to use a shell function and pipe the output to cat
which disconnects ansible
from the terminal and may cause it to not spam colors:
function ansible-playbook
command ansible-playbook "$@"
Another kluge is to fiddle with the TERM
, e.g. TERM=vt220 ansible-playbook ...
(this tends to work on older systems, but the color spam alas is present with TERM=vt220
on modern systems and changing the TERM
without knowing what you're getting into is probably a bad idea).
However! From some spelunking under the ansible
sources, ansible is not buggy and does provide an ANSIBLE_NOCOLOR=1
environment variable:
ANSIBLE_NOCOLOR=1 ansible-playbook ...
1
OP's not using xterm, so this answer is not useful.
– Thomas Dickey
Jul 11 '16 at 20:31
1
@ThomasDickey please explain, in detail, howANSIBLE_NOCOLOR=1 ansible...
is not useful on a console.
– thrig
Jul 12 '16 at 13:49
add a comment |
You can specify the color to use in ansible (at least you can with ansible 2.3.1.0).
Open ansible.cfg and go to the section that says [colors]
You should see something like this
[colors]
#highlight = white
#verbose = blue
verbose = green
#warn = bright purple
#error = red
#debug = dark gray
#deprecate = purple
#skip = cyan
#unreachable = red
#ok = green
#changed = yellow
#diff_add = green
#diff_remove = red
#diff_lines = cyan
Just uncomment the text type you want to change and specify the color you want.
add a comment |
Most applications stick to 16 colors (8 dark colors and 8 bright colors) known as ANSI colors, because that's the common denominator supported by almost all terminals. The ANSI standard doesn't specify the exact shade, it just says “black”, “blue”, “red”, etc. The default blue shade is often a pure blue that is hard to read on a black background on an RGB monitor, but good terminal emulators let you configure the colors. Adding a little bit of red and green into the color is typically enough to make it readable but still distinct.
With xterm, PuTTY, and other compatible terminals, you can configure the colors from an application running inside the terminal by emitting the proper escape sequence. Try running this in the terminal before you start the application:
## Set the blue hue (color 4) to CornflowerBlue
printf 'e]4;4;#6495eda'
If you run bash when you open the terminal, put this in your .bashrc
. If the ansible application opens a terminal on its own, make it print this escape sequence to the terminal.
Alternatively, many terminals let you configure the colors in their configuration, for example through X resources in Xterm. Check the documentation of your terminal emulator.
going straight in my .bashrc file
– lsh
Aug 2 '17 at 11:39
add a comment |
If you are using putty as ssh client, you can simply change its appearance settings.
Change Settings -> Window -> Colours. In the box titled 'Select a colour to adjust:', select 'ANSI Blue' to change the color.
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:16
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f295170%2fhow-can-i-change-the-color-of-this-blue-text-on-my-command-line%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Nope, never have been able to read blue on black (and life is far too short to fiddle with colour customizations in every terminal or console combination I might use) so I disable colors by default. With xterm
, an .Xdefaults
entry of:
XTerm*colorMode:false
does wonders; otherwise, without a means to kill the colors in the terminal, application specific hacks may be necessary; a quick kluge is to use a shell function and pipe the output to cat
which disconnects ansible
from the terminal and may cause it to not spam colors:
function ansible-playbook
command ansible-playbook "$@"
Another kluge is to fiddle with the TERM
, e.g. TERM=vt220 ansible-playbook ...
(this tends to work on older systems, but the color spam alas is present with TERM=vt220
on modern systems and changing the TERM
without knowing what you're getting into is probably a bad idea).
However! From some spelunking under the ansible
sources, ansible is not buggy and does provide an ANSIBLE_NOCOLOR=1
environment variable:
ANSIBLE_NOCOLOR=1 ansible-playbook ...
1
OP's not using xterm, so this answer is not useful.
– Thomas Dickey
Jul 11 '16 at 20:31
1
@ThomasDickey please explain, in detail, howANSIBLE_NOCOLOR=1 ansible...
is not useful on a console.
– thrig
Jul 12 '16 at 13:49
add a comment |
Nope, never have been able to read blue on black (and life is far too short to fiddle with colour customizations in every terminal or console combination I might use) so I disable colors by default. With xterm
, an .Xdefaults
entry of:
XTerm*colorMode:false
does wonders; otherwise, without a means to kill the colors in the terminal, application specific hacks may be necessary; a quick kluge is to use a shell function and pipe the output to cat
which disconnects ansible
from the terminal and may cause it to not spam colors:
function ansible-playbook
command ansible-playbook "$@"
Another kluge is to fiddle with the TERM
, e.g. TERM=vt220 ansible-playbook ...
(this tends to work on older systems, but the color spam alas is present with TERM=vt220
on modern systems and changing the TERM
without knowing what you're getting into is probably a bad idea).
However! From some spelunking under the ansible
sources, ansible is not buggy and does provide an ANSIBLE_NOCOLOR=1
environment variable:
ANSIBLE_NOCOLOR=1 ansible-playbook ...
1
OP's not using xterm, so this answer is not useful.
– Thomas Dickey
Jul 11 '16 at 20:31
1
@ThomasDickey please explain, in detail, howANSIBLE_NOCOLOR=1 ansible...
is not useful on a console.
– thrig
Jul 12 '16 at 13:49
add a comment |
Nope, never have been able to read blue on black (and life is far too short to fiddle with colour customizations in every terminal or console combination I might use) so I disable colors by default. With xterm
, an .Xdefaults
entry of:
XTerm*colorMode:false
does wonders; otherwise, without a means to kill the colors in the terminal, application specific hacks may be necessary; a quick kluge is to use a shell function and pipe the output to cat
which disconnects ansible
from the terminal and may cause it to not spam colors:
function ansible-playbook
command ansible-playbook "$@"
Another kluge is to fiddle with the TERM
, e.g. TERM=vt220 ansible-playbook ...
(this tends to work on older systems, but the color spam alas is present with TERM=vt220
on modern systems and changing the TERM
without knowing what you're getting into is probably a bad idea).
However! From some spelunking under the ansible
sources, ansible is not buggy and does provide an ANSIBLE_NOCOLOR=1
environment variable:
ANSIBLE_NOCOLOR=1 ansible-playbook ...
Nope, never have been able to read blue on black (and life is far too short to fiddle with colour customizations in every terminal or console combination I might use) so I disable colors by default. With xterm
, an .Xdefaults
entry of:
XTerm*colorMode:false
does wonders; otherwise, without a means to kill the colors in the terminal, application specific hacks may be necessary; a quick kluge is to use a shell function and pipe the output to cat
which disconnects ansible
from the terminal and may cause it to not spam colors:
function ansible-playbook
command ansible-playbook "$@"
Another kluge is to fiddle with the TERM
, e.g. TERM=vt220 ansible-playbook ...
(this tends to work on older systems, but the color spam alas is present with TERM=vt220
on modern systems and changing the TERM
without knowing what you're getting into is probably a bad idea).
However! From some spelunking under the ansible
sources, ansible is not buggy and does provide an ANSIBLE_NOCOLOR=1
environment variable:
ANSIBLE_NOCOLOR=1 ansible-playbook ...
edited Dec 12 '17 at 14:51
answered Jul 11 '16 at 15:42
thrigthrig
24.8k23157
24.8k23157
1
OP's not using xterm, so this answer is not useful.
– Thomas Dickey
Jul 11 '16 at 20:31
1
@ThomasDickey please explain, in detail, howANSIBLE_NOCOLOR=1 ansible...
is not useful on a console.
– thrig
Jul 12 '16 at 13:49
add a comment |
1
OP's not using xterm, so this answer is not useful.
– Thomas Dickey
Jul 11 '16 at 20:31
1
@ThomasDickey please explain, in detail, howANSIBLE_NOCOLOR=1 ansible...
is not useful on a console.
– thrig
Jul 12 '16 at 13:49
1
1
OP's not using xterm, so this answer is not useful.
– Thomas Dickey
Jul 11 '16 at 20:31
OP's not using xterm, so this answer is not useful.
– Thomas Dickey
Jul 11 '16 at 20:31
1
1
@ThomasDickey please explain, in detail, how
ANSIBLE_NOCOLOR=1 ansible...
is not useful on a console.– thrig
Jul 12 '16 at 13:49
@ThomasDickey please explain, in detail, how
ANSIBLE_NOCOLOR=1 ansible...
is not useful on a console.– thrig
Jul 12 '16 at 13:49
add a comment |
You can specify the color to use in ansible (at least you can with ansible 2.3.1.0).
Open ansible.cfg and go to the section that says [colors]
You should see something like this
[colors]
#highlight = white
#verbose = blue
verbose = green
#warn = bright purple
#error = red
#debug = dark gray
#deprecate = purple
#skip = cyan
#unreachable = red
#ok = green
#changed = yellow
#diff_add = green
#diff_remove = red
#diff_lines = cyan
Just uncomment the text type you want to change and specify the color you want.
add a comment |
You can specify the color to use in ansible (at least you can with ansible 2.3.1.0).
Open ansible.cfg and go to the section that says [colors]
You should see something like this
[colors]
#highlight = white
#verbose = blue
verbose = green
#warn = bright purple
#error = red
#debug = dark gray
#deprecate = purple
#skip = cyan
#unreachable = red
#ok = green
#changed = yellow
#diff_add = green
#diff_remove = red
#diff_lines = cyan
Just uncomment the text type you want to change and specify the color you want.
add a comment |
You can specify the color to use in ansible (at least you can with ansible 2.3.1.0).
Open ansible.cfg and go to the section that says [colors]
You should see something like this
[colors]
#highlight = white
#verbose = blue
verbose = green
#warn = bright purple
#error = red
#debug = dark gray
#deprecate = purple
#skip = cyan
#unreachable = red
#ok = green
#changed = yellow
#diff_add = green
#diff_remove = red
#diff_lines = cyan
Just uncomment the text type you want to change and specify the color you want.
You can specify the color to use in ansible (at least you can with ansible 2.3.1.0).
Open ansible.cfg and go to the section that says [colors]
You should see something like this
[colors]
#highlight = white
#verbose = blue
verbose = green
#warn = bright purple
#error = red
#debug = dark gray
#deprecate = purple
#skip = cyan
#unreachable = red
#ok = green
#changed = yellow
#diff_add = green
#diff_remove = red
#diff_lines = cyan
Just uncomment the text type you want to change and specify the color you want.
answered Aug 9 '17 at 0:18
TryHarderTryHarder
17113
17113
add a comment |
add a comment |
Most applications stick to 16 colors (8 dark colors and 8 bright colors) known as ANSI colors, because that's the common denominator supported by almost all terminals. The ANSI standard doesn't specify the exact shade, it just says “black”, “blue”, “red”, etc. The default blue shade is often a pure blue that is hard to read on a black background on an RGB monitor, but good terminal emulators let you configure the colors. Adding a little bit of red and green into the color is typically enough to make it readable but still distinct.
With xterm, PuTTY, and other compatible terminals, you can configure the colors from an application running inside the terminal by emitting the proper escape sequence. Try running this in the terminal before you start the application:
## Set the blue hue (color 4) to CornflowerBlue
printf 'e]4;4;#6495eda'
If you run bash when you open the terminal, put this in your .bashrc
. If the ansible application opens a terminal on its own, make it print this escape sequence to the terminal.
Alternatively, many terminals let you configure the colors in their configuration, for example through X resources in Xterm. Check the documentation of your terminal emulator.
going straight in my .bashrc file
– lsh
Aug 2 '17 at 11:39
add a comment |
Most applications stick to 16 colors (8 dark colors and 8 bright colors) known as ANSI colors, because that's the common denominator supported by almost all terminals. The ANSI standard doesn't specify the exact shade, it just says “black”, “blue”, “red”, etc. The default blue shade is often a pure blue that is hard to read on a black background on an RGB monitor, but good terminal emulators let you configure the colors. Adding a little bit of red and green into the color is typically enough to make it readable but still distinct.
With xterm, PuTTY, and other compatible terminals, you can configure the colors from an application running inside the terminal by emitting the proper escape sequence. Try running this in the terminal before you start the application:
## Set the blue hue (color 4) to CornflowerBlue
printf 'e]4;4;#6495eda'
If you run bash when you open the terminal, put this in your .bashrc
. If the ansible application opens a terminal on its own, make it print this escape sequence to the terminal.
Alternatively, many terminals let you configure the colors in their configuration, for example through X resources in Xterm. Check the documentation of your terminal emulator.
going straight in my .bashrc file
– lsh
Aug 2 '17 at 11:39
add a comment |
Most applications stick to 16 colors (8 dark colors and 8 bright colors) known as ANSI colors, because that's the common denominator supported by almost all terminals. The ANSI standard doesn't specify the exact shade, it just says “black”, “blue”, “red”, etc. The default blue shade is often a pure blue that is hard to read on a black background on an RGB monitor, but good terminal emulators let you configure the colors. Adding a little bit of red and green into the color is typically enough to make it readable but still distinct.
With xterm, PuTTY, and other compatible terminals, you can configure the colors from an application running inside the terminal by emitting the proper escape sequence. Try running this in the terminal before you start the application:
## Set the blue hue (color 4) to CornflowerBlue
printf 'e]4;4;#6495eda'
If you run bash when you open the terminal, put this in your .bashrc
. If the ansible application opens a terminal on its own, make it print this escape sequence to the terminal.
Alternatively, many terminals let you configure the colors in their configuration, for example through X resources in Xterm. Check the documentation of your terminal emulator.
Most applications stick to 16 colors (8 dark colors and 8 bright colors) known as ANSI colors, because that's the common denominator supported by almost all terminals. The ANSI standard doesn't specify the exact shade, it just says “black”, “blue”, “red”, etc. The default blue shade is often a pure blue that is hard to read on a black background on an RGB monitor, but good terminal emulators let you configure the colors. Adding a little bit of red and green into the color is typically enough to make it readable but still distinct.
With xterm, PuTTY, and other compatible terminals, you can configure the colors from an application running inside the terminal by emitting the proper escape sequence. Try running this in the terminal before you start the application:
## Set the blue hue (color 4) to CornflowerBlue
printf 'e]4;4;#6495eda'
If you run bash when you open the terminal, put this in your .bashrc
. If the ansible application opens a terminal on its own, make it print this escape sequence to the terminal.
Alternatively, many terminals let you configure the colors in their configuration, for example through X resources in Xterm. Check the documentation of your terminal emulator.
answered Jul 12 '16 at 0:07
GillesGilles
535k12810821599
535k12810821599
going straight in my .bashrc file
– lsh
Aug 2 '17 at 11:39
add a comment |
going straight in my .bashrc file
– lsh
Aug 2 '17 at 11:39
going straight in my .bashrc file
– lsh
Aug 2 '17 at 11:39
going straight in my .bashrc file
– lsh
Aug 2 '17 at 11:39
add a comment |
If you are using putty as ssh client, you can simply change its appearance settings.
Change Settings -> Window -> Colours. In the box titled 'Select a colour to adjust:', select 'ANSI Blue' to change the color.
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:16
add a comment |
If you are using putty as ssh client, you can simply change its appearance settings.
Change Settings -> Window -> Colours. In the box titled 'Select a colour to adjust:', select 'ANSI Blue' to change the color.
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:16
add a comment |
If you are using putty as ssh client, you can simply change its appearance settings.
Change Settings -> Window -> Colours. In the box titled 'Select a colour to adjust:', select 'ANSI Blue' to change the color.
If you are using putty as ssh client, you can simply change its appearance settings.
Change Settings -> Window -> Colours. In the box titled 'Select a colour to adjust:', select 'ANSI Blue' to change the color.
answered Jan 23 '17 at 1:09
geo.cgeo.c
211
211
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:16
add a comment |
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:16
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:16
Welcome to Unix.stackexchange! I recommend you take the tour.
– Stephen Rauch
Jan 23 '17 at 1:16
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f295170%2fhow-can-i-change-the-color-of-this-blue-text-on-my-command-line%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
blue over the background shall be visible, although in this case is isn't. Do not try to use shell escapes to change the colours. You need to configure the
blue color
in your terminal emulator to something more visible.– grochmal
Jul 11 '16 at 15:24
@grochmal thanks for the input. How can I do that? Is it LS_Colors or with tput or..... ?
– Joze
Jul 11 '16 at 15:30
Which terminal emulator are you using?
– derobert
Jul 11 '16 at 15:32
@derobert Kitty
– Joze
Jul 11 '16 at 15:32
1
halyph.blogspot.com/2013/01/custom-puttykitty-color-scheme.html ... looks like you should have a settings entry to change the colors. (Really probably off-topic here, at least if editing the KiTTY config turns out to be the answer).
– derobert
Jul 11 '16 at 15:35