and if you want even more color (colorized output for common cli apps), install cope! On Thu, Aug 19, 2010 at 7:48 PM, Phillip Thelen wrote:

Have you tried adding this to your .bashrc?

alias ls='ls --color=auto'

basically just tells bash to execute "ls --color=auto" instead of just ls.

Hope that helps you ;)

mfg vIiRuS

On 08/20/2010 02:43 AM, Carlos Mennens wrote:

...

It's very frustrating in Arch that my directories[blue], text files[white], tarballs[red], symbolic links[blue], and scripts[green] are all the same color. How can I colorize this in bash so my Arch Linux system is much easier to sort through?

I checked the Wiki and only found something about colorizing my PS1 which is not what I really care about.

Thanks for any help...

for root, you need to create it yourself. it will be created for users you add to the system however. if you do create one for root, you'll have to create a .bash_profile file as well that sources it for it to actually work automagically on login. On Thu, Aug 19, 2010 at 7:50 PM, Carlos Mennens wrote:

On Thu, Aug 19, 2010 at 8:48 PM, Phillip Thelen wrote:

...

Have you tried adding this to your .bashrc?

alias ls='ls --color=auto'

basically just tells bash to execute "ls --color=auto" instead of just ls.

Hope that helps you ;)

Right now I only have a 'root' user and no normal shell users ...yet. I checked /root and there is not /root/.bash*. Am I missing something here? I even created a new user and in their home directory there is no .bashrc. What is wrong with my system or am I expected to manually create the .bashrc file using 'vim'?

true, but then he doesn't learn anything :P On Thu, Aug 19, 2010 at 7:57 PM, Phillip Thelen wrote:

check /etc/skel/.bashrc. You should be able to use that one as a base file. simply copy it to the /root direcory or the $Home Directory of a user.

On 08/20/2010 02:50 AM, Carlos Mennens wrote:

...

On Thu, Aug 19, 2010 at 8:48 PM, Phillip Thelen wrote:

...

Have you tried adding this to your .bashrc?

alias ls='ls --color=auto'

basically just tells bash to execute "ls --color=auto" instead of just ls.

Hope that helps you ;) Right now I only have a 'root' user and no normal shell users ...yet. I checked /root and there is not /root/.bash*. Am I missing something here? I even created a new user and in their home directory there is no .bashrc. What is wrong with my system or am I expected to manually create the .bashrc file using 'vim'?

if you want to customize the colors of ls output, edit the LS_COLORS env variable. details here : http://www.linux-sxs.org/housekeeping/lscolors.html you can place that in your .bashrc, and you can set very usefull reg exp, like "*.log", ...

ls --color | less => colorized output

Cheers, Emmanuel

Guys, does ArchLinux source ~/.profile file? If not, why? I better prefer to set i.e. aliases for all my shells, not only BASH… -- Jabber: reflexing@reflexing.ru, ICQ: 8163230, Skype on demand.

On Fri, Aug 20, 2010 at 10:03:30AM -0400, Dave Reisner wrote:

On Fri, Aug 20, 2010 at 07:53:17PM +0600, reflexing wrote:

...

Guys, does ArchLinux source ~/.profile file? If not, why? I better prefer to set i.e. aliases for all my shells, not only BASH…

-- Jabber: reflexing@reflexing.ru, ICQ: 8163230, Skype on demand.

Read the INVOCATION section of bash(1).

d

Er, that is to say.. it has nothing to do with your distro. Sourcing files out of your home directory is reliant on the shell. d

On Fri, Aug 20, 2010 at 08:07:02PM +0600, reflexing wrote:

On Fri, Aug 20, 2010 at 8:04 PM, Dave Reisner wrote:

...

On Fri, Aug 20, 2010 at 10:03:30AM -0400, Dave Reisner wrote:

...

On Fri, Aug 20, 2010 at 07:53:17PM +0600, reflexing wrote:

...

Guys, does ArchLinux source ~/.profile file? If not, why? I better prefer to set i.e. aliases for all my shells, not only BASH…

-- Jabber: reflexing@reflexing.ru, ICQ: 8163230, Skype on demand.

Read the INVOCATION section of bash(1).

d

Er, that is to say.. it has nothing to do with your distro. Sourcing files out of your home directory is reliant on the shell.

d

It worked for me in RHEL but didn't worked in ArchLinux, please confirm.

-- Jabber: reflexing@reflexing.ru, ICQ: 8163230, Skype on demand.

Since you didn't read the man page, I'll quote it here for you: When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes com‐ mands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.pro‐ file, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. Short form: if .bash_profile and/or .bash_login exist, .profile will never be read. Again, this is all distro agnostic. d