[SOLVED] No colors in ls output

alexbrui · 04-15-2011, 07:55 AM

Using Slackware 13.1 and rxvt-unicode as terminal emulator. There is no colors in ls output under user but running ls as root gives color output.

I check that /etc/profile.d/coreutils-dircolors.sh has executable bit, and LS_OPTIONS environment variable is correct

Code:

bash-4.1$ echo $LS_OPTIONS                     
-F -b -T 0 --color=auto

Running ls with --color option gives me color output. As I can see /etc/profile.d/coreutils-dircolors.sh should set up aliases for ls, dir and vdir commands but why this aliases don't work under user?

smallpond · 04-15-2011, 08:02 AM

Run the alias command to see what options are set in ls. If there is no ls alias add this to your startup (~/.bashrc is good)

alias ls='ls -F --color=auto'

The system version is this:
alias ls='ls -F --color=auto' 2>/dev/null

which won't give an error about colors in case you are logging in on a teletype.

dh2k · 04-15-2011, 08:02 AM

see my post:

http://www.linuxquestions.org/questi...prompt-798622/

You can add to your '~/.bashrc':

Code:

. /etc/profile

T3slider · 04-15-2011, 01:53 PM

Subsequent bash shells inherit environment variables from the initial login shell (so running `. /etc/profile` isn't the best solution, since things like $XDG_CONFIG_DIRS end up having duplicated paths), but they do not inherit aliases. Therefore, you should place the aliases from /etc/profile.d/*.sh (or *.csh if you use a c shell) in your ~/.bashrc (or other non-login shell init file).

Code:

$ grep -vh "^[[:space:]]*#" /etc/profile.d/*.sh | grep alias
  alias ls='/bin/ls ${=LS_OPTIONS}'
  alias dir='/bin/ls ${=LS_OPTIONS} --format=vertical'
  alias vdir='/bin/ls ${=LS_OPTIONS} --format=long'
  alias ls='/bin/ls $LS_OPTIONS'
  alias dir='/bin/ls $LS_OPTIONS --format=vertical'
  alias vdir='/bin/ls $LS_OPTIONS --format=long'
alias d=dir
alias v=vdir
alias mc='. /usr/share/mc/bin/mc-wrapper.sh'

That output grabs all of the aliases in Slackware 13.1.

Code:

$ find /etc/profile.d/ -executable -name "*.sh" -exec grep -h alias {} \; | grep -v "^[[:space:]]*#"

should grab aliases only from executable .sh files in /etc/profile.d.

rfernandez · 04-15-2011, 03:40 PM

I always solve this problem by initiating the console as a login shell. In Konsole, I always use

Code:

/bin/bash -l

alexbrui · 04-16-2011, 01:21 AM

Thanks guys. I create aliases in my ~/.bashrc file

GazL · 04-16-2011, 03:36 AM

Quote:

Originally Posted by T3slider

Code:

$ grep -vh "^[[:space:]]*#" /etc/profile.d/*.sh | grep alias
  alias ls='/bin/ls ${=LS_OPTIONS}'
  alias dir='/bin/ls ${=LS_OPTIONS} --format=vertical'
  alias vdir='/bin/ls ${=LS_OPTIONS} --format=long'
  alias ls='/bin/ls $LS_OPTIONS'
  alias dir='/bin/ls $LS_OPTIONS --format=vertical'
  alias vdir='/bin/ls $LS_OPTIONS --format=long'
alias d=dir
alias v=vdir
alias mc='. /usr/share/mc/bin/mc-wrapper.sh'

That output grabs all of the aliases in Slackware 13.1.

Including some you wouldn't want in a .bashrc. Those first 3 ls aliases are variants for zsh that use a zsh specific syntax (it does word splitting differently)
.
Might be better just to do this as a one off and then edit the resulting .bashrc to taste

Code:

bash -l -c alias >> ~/.bashrc

or, if you don't want to tailor it and just want the aliases to be inherited as is from /etc/profile + /etc/profile.d/*.sh just add the following line to the top of your .bashrc

Code:

source <( bash -l -c alias )

I agree with your other points though. .bashrc is the appropriate place for them, and for the bash specific PS1= string which really shouldn't be exported from /etc/profile
(To see why exporting the PS1 string is a bad idea; run a 'bash -l' and then from within that shell start either ash or ksh.)

To tie things together nicely I use a ~/.bash_profile as follows:

Code:

case $- in
*i* )  # Interactive shell
       if [ -f ~/.bashrc ]; then
          source ~/.bashrc
       fi
       ;;
esac

and then my aliases/PS1 defined in ~/.bashrc

T3slider · 04-16-2011, 01:56 PM

Woops, sorry for the oversight and thank you for correcting it. As for PS1, I guess Pat assumes that most people will stick to whatever shell is defined as their login shell, but I see your point.