update README with shell info and add a cool term gif

1 files changed, 21 insertions, 2 deletions

diff --git a/README.md b/README.md
index f429bd7..89bf862 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@
  ░▓ code   ▓ http://code.xero.nu/dotfiles
  ░▓ mirror ▓ http://git.io/.files
  ░▓▓▓▓▓▓▓▓▓▓
- ░░░░░░░░░░
+ ░░░░░░░░░░https://github.com/xero/dotfiles#how-it-works
 
  awesome        > awesome wm config and ghost theme
  compton        > minimal composite config for opacity
@@ -44,6 +44,16 @@
  zsh            > zshell settings, aliases, and custom prompts
 ```
 
+##table of contents
+ - [introduction](#dotfiles)
+ - [managing](#managing)
+ - [installing](#installing)
+ - [how it works](#how-it-works)
+ - [tl;dr](#tldr)
+ - [my shell](#my-shell)
+ - [vim](#vim)
+ - [previews](#previews)
+
 #dotfiles
 in the unix world programs are commonly configured in two different ways, via shell arguments or text based configuration files. programs with many options like window managers or text editors are configured on a per-user basis with files in your home directory `~`. in unix like operating systems any file or directory name that starts with a period or full stop character is considered hidden, and in a default view will not be displayed. thus the name dotfiles. 
 
@@ -118,8 +128,17 @@ install herbstluftwm
 
 `stow herbstluftwm`
 
+etc, etc, etc...
+
+#my shell
+i prefer a minimal setup, and choose to interact with my operating system via the so-called "terminal" or "command line", (read that quoting sarcastically) over a gui interface 2 times out of 3. with the web browser and video player among the noted outliers. in my opinion, using your computer should be a very personal experience. your colors, aliases, key-bindings, etc meticulously crafted to your exacting specifications. so for me, the unix shell is the most important part of my environment.
+
+![](https://raw.githubusercontent.com/xero/dotfiles/master/previews/xero_shell.gif)
+
+my terminal emulator of choice is the lightweight, unicode, 256 color [urxvt](http://linux.die.net/man/1/urxvt). i use [zsh](http://linux.die.net/man/1/zsh) as my interactive shell. it's an extensible, bash like shell with awesome completion and correction engines. i manage multiple shell sessions with [tmux](http://linux.die.net/man/1/tmux). it's a feature packed terminal multiplexer with support for buffers, split windows, detached local and remote sessions, etc. i'm a member of the cult of [vim](http://linux.die.net/man/1/vim). sing phrases to the third reincarnation of the glorious ed! lel. [mpd](http://linux.die.net/man/1/mpd) is my music server and i use [ncmpcpp](http://ncmpcpp.rybczak.net/) as it's frontend. my configs for [urxvt](http://git.io/.urxvt), [zsh](http://git.io/.zsh), [tmux](http://git.io/.tmux), [vim](http://git.io/.vim), [mpd](http://git.io/.mpd) and [ncmpcpp](http://git.io/.ncmpcpp) shown above feature my [sourcerer](http://sourcerer.xero.nu) color scheme.
+
 #vim
-[vim](http://www.vim.org), with it's tight integration to the unix shell, has quickly become my editor of choice. once you start to master the movements and operators you quickly begin manipulating, not just editing, source code files.
+with it's tight integration to the unix shell, [vim](http://www.vim.org) has quickly become my editor of choice. once you start to master the movements and operators you quickly begin manipulating, not just editing source code files.
 
 when you learn vim it's best to use a more vanilla config. if helps you focus on learning the editor and not the plugins. these are also great for [remote machines](http://git.io/.vimrc-min). but for your local dev environment, vim's vast and powerful plugin system can add many great features. i try to keep my editor slim and fast, but i find myself loving these plugins: