`RBENV_ROOT` can be used to relocate where rbenv ends up storing the shims
and versions of Ruby it installs. Because of this split `RBENV_ROOT`
cannot be used to reliably construct a path to the rbenv binary itself.

Instead we now rely on `$RBENV_BIN_ROOT` pointing to the `bin/` directory
containing the rbenv binary/script.

If `$RBENV_BIN_ROOT` is not set we search `$PATH` first and then the
user's home directory making sure to prepend the necessary directories to
our `$PATH` depending on where we find rbenv.

Lastly we prepend to our `$PATH` the location rbenv's `shims/` so that we
can find the shims rbenv generates for us.

contributing guidelines

Add preview image for coffeeandcode theme.

Fixed broken image URL in README.md on theme Zish

Assigning a default value to TRAVIS_BRANCH

correctly checkout branch on travis install

seq call in getopts should specify negative step

adding a dockerfile

~ fish getopts plugin ~ 

add OSX emoji workaround to README

Theme Edan: Update with optional "user & host" info.

Switch using `edan-remote` or `edan-local`

test runner should search fish_path for specs instead of *

added osx plugin