That's what I get. So, let's test this thing out by seeing what envs
we have.

Let's try it:

$ rip-envs
$RIPDIR not set. Please eval `rip-shell`

Whoops. We need to restart our shell so the ~/.bashrc changes take
hold. We can also run that eval command by hand, but it's easier
just to open a new shell.

Now, in our new shell:

$ rip-envs
/Users/chris/.rip not found. Please run `rip-setup`

Okay.

$ rip-setup
$ rip-envs
* base

We're ready to roll.

Disabling rip

Many people installed Rip, played with it, realized it wasn't done,
then forgot about it - only to become frustrated when some package
they installed with Rip screwed up their development
environment. Those were the kinds of problems Rip was supposed to
solve! What does rip2 have to say about this?

Two words: rip-off. rip2 can be enabled or disabled at any time
using the rip-off and rip-on commands: