Changed shell color, now have display errors

Question

I put in place color codes on our Centos7 servers with a file in /etc/profile.d/file.sh :

export PS1="\e[1;36m[\u@\h \W]\$ \e[m "

Thing is, now, when I go through my CLI history after typing in a command as root, it will not replace all of the command, which makes it hard to read.

Example : I would type

sudo yum install php php-cli

Then type something else. Then if i want to go back in the history using the up arrow on my keyboard, I will end up having things like :

sudo yum ils-l
sudo yum ips aux |grep total
sudo yum icat /var/log/httpd

Instead of

ls -l
ps aux | grep total
cat /var/log/httpd

I assume the two are linked, but I can't manage to understand what I'm missing.

Side note: There is no reason to `export` the `PS1` variable. — Kusalananda, Aug 09 '16 at 11:24
If the `<%= @color %>` in your PS1 is replaced by something else, you should post the resulting PS1 (e. g. from `set|grep PS1`), because only that matters. And are you using some other shell than `bash`? — Armali, Aug 10 '16 at 06:31
Updated OP with correct PS1. Only using bash. Thanks for the answers — Paul-antoine Kempf, Aug 10 '16 at 14:15

score 0 · Answer 1 · edited May 23 '17 at 12:00

0

<%= @color %> is not a valid syntax for a color mode number; replace that by a number from 30 to 37; see List of ANSI color escape sequences.

edited May 23 '17 at 12:00

Community

1
1

answered Aug 09 '16 at 11:10

Armali

18,255
14
57
171

sorry, it's the chef notation. It actually is a number. – Paul-antoine Kempf Aug 09 '16 at 15:30
@Paul-antoine Kempf: I would not be so sure about that - if it actually were a number, the PS1 would be correct. See my comment to the question. – Armali Aug 10 '16 at 06:27

Changed shell color, now have display errors

1 Answers1