Terminal Tweaks
Oct 30th, 2009 by mark
While the Apple Mac OS X graphical user interface is beautiful and very easy to use, having a powerful Unix command line at my disposal gives OS X something extra. Out of the box Terminal (Applications -> Utilities -> Terminal) is ready to go, but I like to customize all parts of my computer, so here is what I’ve done to Terminal.
Terminal Style
I use a colored theme to provide high contrast in my Terminal window. This improves readability tremendously. The theme I like currently is called GiovanniStyle. It uses light yellow on a dark blue background. While the author suggests Consolas for the font I am using Anonymous Pro. Consolas comes with Microsoft Office which I don’t have installed. There is a free font called Inconsolas that mimics the Microsoft offering, but I still like the Anonymous appearance better.
Manpages Color
The only drawback to GiovanniStyle is view manpages. By default some of the colors used in man’s output is not contrasty enough to be legible. Consequently I added a section to my .bash_profile to compensate. Here are the color designations I’m using for manpages:
# Color man pages: export LESS_TERMCAP_mb=$'\E[01;31m' Â Â Â # begin blinking export LESS_TERMCAP_md=$'\E[01;31m' Â Â Â # begin bold export LESS_TERMCAP_me=$'\E[0m' Â Â Â Â Â # end mode export LESS_TERMCAP_se=$'\E[0m' Â Â Â Â Â # end standout-mode export LESS_TERMCAP_so=$'\E[01;44;33m' Â # begin standout-mode - info box export LESS_TERMCAP_ue=$'\E[0m' Â Â Â Â Â # end underline export LESS_TERMCAP_us=$'\E[01;32m' Â Â Â # begin underline
And here’s the output:
My Prompt
Speaking of bash, I’ve modified my prompt, to make it standout more and to provide the information about who I’m logged in as and what my current working directory is, in a manner pleasing to me. Here’s the prompt:
PS1='\[\e]0;\w\a\]\n\[\e[32m\]\u@\H \[\e[33m\]\w\[\e[0m\]\n$\[\033]0;\u@\h:\w\007\] '
And here’s what it looks like:
.bash_profile and .bashrc
I do not pretend to understand (yet) all the ins and outs of what goes in a .bash_profile and what goes in a .bashrc file. With that disclaimer in mind, I know the .bash_profile is the personal initialization file, which is executed for login shells, and the .bashrc file is the individual per-interactive-shell startup file. In my case I tend to have PATH additions and exports in .bash_profile, while keeping aliases and functions in my .bashrc.
This is my current .bash_profile:
# .profile # get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi # set PATH so it includes user's private bin if it exists if [ -d ~/bin ] ; then PATH="~/bin:${PATH}" fi # set PATH so it includes /usr/local/sbin if it exists if [ -d /usr/local/sbin ] ; then PATH="/usr/local/sbin:${PATH}" fi # set PATH so it includes /usr/local/bin if it exists if [ -d /usr/local/bin ] ; then PATH="/usr/local/bin:${PATH}" fi export PATH # user specific environment and startup programs # setup for java JAVA_HOME=/Library/Java/Home # configure how history works HISTCONTROL=ignoredups # ignore the line if it matches previous line HISTFILESIZE=20000 # size of the history file cf. also shopt -s histappend HISTSIZE=1000 # size of the run-time history list HISTIGNORE=ls:ll:la:l:cd:pwd:exit:mc:su:df:clear # do not put these in history file # add colors to terminal (see man ls for details) CLICOLOR=1 # Order: # 1. directory, 2. symbolic link, 3. socket, 4. pipe, 5. executable, # 6. block special, 7. character special 8. executabel with setuid # bit set, 9. executable with setgid bit set, 10. directory writable # to others, with sticky bit 11. directory writable to others, # without sticky bit # # Colors # a - black, b - red, c - green, d - brown (yellow), e - blue, f - magenta, # g - cyan, h - light grey # A - Bold black, B - Bold red, C - Bold green, D - Bold brown (yellow), # E - Bold blue, F - Bold Magenta, G - Bold cyan, # H - Bold light grey (appears bright white), x - default color LSCOLORS=gxFxCxDxBxegedabagacad # export settings export JAVA_HOME HISTCONTROL HISTFILESIZE HISTSIZE HISTIGNORE CLICOLOR LSCOLORS # Color man pages: export LESS_TERMCAP_mb=$'\E[01;31m' # begin blinking export LESS_TERMCAP_md=$'\E[01;31m' # begin bold export LESS_TERMCAP_me=$'\E[0m' # end mode export LESS_TERMCAP_se=$'\E[0m' # end standout-mode export LESS_TERMCAP_so=$'\E[01;44;33m' # begin standout-mode - info box export LESS_TERMCAP_ue=$'\E[0m' # end underline export LESS_TERMCAP_us=$'\E[01;32m' # begin underline
And this is my current .bashrc file:
# user specific functions and aliases # source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi # prompts # set prompt: user@host working directory new line $ using colors # also set title to user@host and display current directory PS1='\[\e]0;\w\a\]\n\[\e[32m\]\u@\H \[\e[33m\]\w\[\e[0m\]\n$\[\033]0;\u@\h:\w\007\] ' # some alias settings, just for fun #alias 'today=calendar -A 0 -f ~/calendar/calendar.mark | sort' alias 'today=calendar -A 0 -f /usr/share/calendar/calendar.mark | sort' alias 'dus=du -sckx * | sort -nr' alias 'adventure=emacs -batch -l dunnet' alias 'mailsize=du -hs ~/Library/mail' alias 'bk=cd $OLDPWD' # function to force prompt before overwriting function r() { rm -i $1 } alias 'rm=rm -i'
The calendar alias runs the calendar command against a calendar file of my own making. I just copied the calender.all file in
/usr/share/calendar
and eliminated the calendars I wasn’t interested in seeing and called the new file calendar.mark.
The dus alias produces a list of directories and files sorted into order from largest to smallest. It recurses through all sub-directories from where it is run, i.e., running it from your home directory could take a while depending on your processor and the number of files on your system. You can add an -h flag to the du command to get a human-readable output, but that breaks the sorting.
Adventure is fun, you should give it a try. Don’t blame me however, if you get eaten by a grue.
Mailsize spits out the current size of your mail directory. I’m up to 5 GB myself.
bk takes you back to the previous directory. It’s the same as cd - only shorter.
The r function and the rm alias are measures designed to protect me from careless use of the remove (rm) command. Be warned that issuing a rm -rf neatly sidesteps these “protections.” Command-line-interfaces are powerful and therefore can be dangerous.