When I was growing up and mastering conventional memory management in DOS for the sole purpose of viewing various graphical demos from around the world, I knew about and how to use every command available within the operating system. Even though that’s probably not realistic these days, it’s something definitely worth shooting for over time (hmmm Linux from Scratch. If the same were true today, then I would have already been using the pbcopy and pbpaste utilities.

Now I can simply pipe the current working directory to the clipboard:

pwd | pbcopy

Open a new terminal tab or window, and use a combination of cd and Command-V or pbpaste to get back to the original directory:

cd `pbpaste`
cd [Command-V]

While pbcopy and pbpaste are excellent utilities, they aren’t the best solution for what I originally set out to do: open a new tab in the current working directory. I’m sure there is an even quicker way to get to the same current working directory, probably with an AppleScript, and I suspect that OS X Lion has an option for this in Terminal, but for now, pbcopy will do the trick.

rbenv subscribes to the Unix philosophy of doing one thing and doing it well. It’s one job is managing multiple installations (and versions) of the Ruby programming language. It does nothing else.

Remove RVM

Since RVM stores everything in a single place, removing it from your system completely is a simple task. In fact, the rvm implode command provides most of this functionality for you.

$ rvm implode
$ sudo rm -rfd /etc/rvmrc
$ rm ~/.rvmrc

Within your .bash_profile (or whatever shell initialization file you typically use), there should be a line that initializes RVM:

[[ -s $HOME/.rvm/scripts/rvm ]] && source $HOME/.rvm/scripts/rvm

Remove it. Farewell, RVM.

Install rbenv

rbenv is easier to install than RVM is to remove. Usually I like to refer to the awesome Homebrew package manager for OS X, and this time is no different.

$ brew update
$ brew install rbenv

Then add the following line to your .bash_profile:

eval "$(rbenv init -)"

rbenv is now installed. Now we need to install some Rubies! Remember when I mentioned that rbenv does one thing (and does it well)? Well, that one thing is MANAGING multiple Ruby versions, not installing them. To give rbenv the capability to install Rubies, you need another tool: ruby-build.

Install ruby-build

Installation of ruby-build is even simpler than rbenv:

$ brew install ruby-build

Install Rubies

Now you can install Rubies all day. Why not write a script to do it? See how fast you can fill up your hard drive with Ruby installations — wouldn’t that be a beautiful thing? Well, it’d probably just be a waste of hard drive space. But in any case …

To see a list of available versions, either of these commands will work:

$ rbenv install
$ ruby-build --definitions

Choose your favorite Ruby and install it:

$ rbenv install 1.9.2-p290
$ rbenv rehash

It’s necessary to run rbenv rehash after installing a new Ruby version or gems that include shell commands. This simply gives rbenv the knowledge it needs to run the correct commands.

If you want to install multiple copies of the same Ruby version, use ruby-build instead:

$ ruby-build 1.9.2-p290 ~/.rbenv/versions/1.9.2-p290-custom

Where “1.9.2-p290-custom” is the directory name where the new version will be installed.

Switch between

Globally:

$ rbenv global 1.9.2-p290
$ rbenv global 1.9.2-p290-custom

Per project:

Add the version name to the .rbenv-version within your project’s directory:

$ echo '1.9.2-p290-custom' > .rbenv-version

Or override the version within the shell completely:

$ export RBENV_VERSION='1.9.2-p290'

More information

For more and up-to-date information, please see the rbenv project page on GitHub.

Nice to meet you, rbenv. Boom goes the dynamite.