# You may want to put all your additions into a separate file like Test -r ~/.dircolors & eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" # enable color support of ls and also add handy aliases # If this is an xterm set the title to "$TERM" \w\a\]$PS1" # a case would tend to support setf rather than setaf.) (Lack of such support is extremely rare, and such # We have color support assume it's compliant with Ecma-48 # should be on the output of commands, not on the prompt # off by default to not distract the user: the focus in a terminal window # uncomment for a colored prompt, if the terminal has the capability turned # set a fancy prompt (non-color, unless we know we "want" color) # set variable identifying the chroot you work in (used in the prompt below) # make less more friendly for non-text input files, see lesspipe(1) ![]() # update the values of LINES and COLUMNS. # check the window size after each command and, if necessary, # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) # append to the history file, don't overwrite it # don't put duplicate lines in the history. # If not running interactively, don't do anything # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) bashrc # ~/.bashrc: executed by bash(1) for non-login shells. bashrc I uncommeneted force_color_prompt=yes, and when I run env | grep TERM I get TERM=xterm-color. I think it happened while I was installing/troubleshooting RVM, but I am not positive. I am accessing an Ubuntu 10.04.2 LTS server via SSH from OSX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |