Colorized Bash Prompts

carlosinfl · 08-19-2010, 07:27 PM

I get really frustrated that in Arch my directories are not blue / purple and my tarball files are not red. How can I colorized my ls output to be more convenient?

konsolebox · 08-19-2010, 08:06 PM

You just need to edit /etc/DIR_COLORS.

For information about ANSI codes, go here: http://en.wikipedia.org/wiki/ANSI_escape_code

I recommend that you backup the file first before edit.

mixtr · 08-20-2010, 10:51 PM

or put this in your .bashrc
alias ls='ls --color=auto"

mixtr · 08-20-2010, 10:52 PM

or put this in your .bashrc
alias ls='ls --color=auto"

papul1993 · 08-21-2010, 11:42 AM

# Check for an interactive session
[ -z "$PS1" ] && return

alias ls='ls --color=auto'
#PS1='[\u@\h \W]\$ '

#PS1='\[\e[1;32m\][\u@\h \W]\$\[\e[0m\] '

PS1='\[\e[1;31m\][\u@\h \W]\$\[\e[0m\] '

^^^^^
this in your ~/.bashrc might help

Meson · 09-09-2010, 07:23 PM

I'm not sure how useful this is, but I've always had

Code:

 eval $(dircolors -b)

in by bashrc (in addition to the ls --color alias)

carlosinfl · 10-04-2010, 11:18 AM

My users all have .bashrc file however my root user doesn't. This is why I can't see colored 'ls' output. If my root use is missing his .bashrc, how can I have my root account be able to see colored 'ls' output?

TobiSGD · 10-04-2010, 11:31 AM

Just make a .bashrc in your /root directory.

carlosinfl · 10-04-2010, 11:33 AM

What needs to be in that file so that root has a colorized 'ls' output?

onebuck · 10-04-2010, 01:35 PM

Hi,

You could setup a .bashrc & .bash_profile for your user(s) & root;

Code:

sample .bash_profile;
 
 ~$ cat .bash_profile
 #-------
 # .bash_profile
 #08-30-06 12:21
 #
 # Source .bashrc
 if [ -f ~/.bashrc ]; then
         . ~/.bashrc
 fi
 #---------

Code:

 sample .bashrc;
 :~$ cat .bashrc
 
 #----------
 #.bashrc
 #08-30-06 12:20 
 
 # Add bin to path
 
 export PATH="$PATH:/sbin:/usr/sbin:$HOME/bin"
 
 #export PATH="$PATH:$HOME/bin"
 
 # Dynamic resizing
 shopt -s checkwinsize
 
 # Custom prompt
 #PS1='\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
 
 #08-29-06 11:40
 
 if [ `id -un` = root ]; then
    PS1='\[\033[1;31m\]\h:\w\$\[\033[0m\] '
  else
    PS1='\[\033[1;32m\]\h:\w\$\[\033[0m\] '
 fi
 
 #
 # Add color
 eval `dircolors -b`
 
 # User defined aliases
 alias cls='clear'
 alias clls='clear; ls'
 alias ll='ls -l'
 alias lsa='ls -A'
 alias lsg='ls | grep'
 alias lsp='ls -1 /var/log/packages/ > package-list'
 alias na='nano'
 alias web='links -g -download-dir ~/ www.google.com'
 
 #08-29-06 11:50
 
 #To clean up and cover your tracks once you log off
 #Depending on your version of BASH, you might have to use
 # the other form of this command
    trap "rm -f ~$LOGNAME/.bash_history" 0
 
 #The older KSH-style form
 #   trap 0 rm -f ~$LOGNAME/.bash_history
 #--------

The .bashrc is very useful!

carlosinfl · 10-04-2010, 02:24 PM

Thanks. I just did:

Code:

cp -a /etc/skel/.bash* /root/

rweaver · 10-04-2010, 02:53 PM

Quote:

Originally Posted by carlosinfl

Thanks. I just did:

Code:

cp -a /etc/skel/.bash* /root/

Make sure your /etc/skel items you copied don't contain items like "PATH=$PATH:~/bin" running as root items like that are fairly dangerous, so be sure you read the files you copied in well and ensure they're doing what they should be done exactly.

onebuck · 10-04-2010, 03:30 PM

Hi,

Quote:

Originally Posted by carlosinfl

Thanks. I just did:

Code:

cp -a /etc/skel/.bash* /root/

You should use a method to differentiate root & user so the PATH is correctly set.

Look at the way the root is tested in the sample to set for color and the way the PATH is set early at the top of the script. You can modify to suit.
In '~' I setup for each user and modify to suit. If you have a lot of users then setup the defaults for system wide. This way you can setup a user to have specific needs with a '~/.bashrc' & '~/.bash_profile'.