mkdir -p ~/Library/Application\ Support/TextMate/Pristine\ Copy/Bundles
cd ~/Library/Application\ Support/TextMate/Pristine\ Copy/Bundles
git clone git://github.com/rspec/rspec-tmbundle.git RSpec.tmbundle
osascript -e 'tell app "TextMate" to reload bundles'
This RSpec.tmbundle works with both rspec-1 and rspec-2. Given
that they work differently, the RSpec.tmbundle tries its best to
figure out which one you're using in each project when you try to
run RSpec examples. There are two separate parts to this process,
and you have some control over how each one works.
The RSpec.tmbundle prepares the LOAD_PATH as follows:
-
If a
Gemfileis present,Bundleris used to prepare the Load Path withrequires 'bundler'and thenBundler.setupis executed. (This can be overridden - see below). -
If
Bundlerisn't being used,vendor/pluginsandvendor/gemsare searched forrspec. Ifrspecis found, then it'slibdirectory is added toLOAD_PATH.
Once the LOAD_PATH is prepared, RSpec-tmbundle tries to
determine which version of RSpec to use as follows:
RSpec-tmbundlechecks for an./rspec-tmfile in the project's root directory. If that file is exists, thenRSpec-tmbundleattempts to set the RSpec version from the configuration found there.
To configure the version using this method add a file named
.rspec-tm to the project's root directory containing:
--rspec-version 2.0.0
or whichever version you are using.
This is the one foolproof way to ensure that the right version is invoked, but you don't really need to do this in most cases.
-
If no version is configured,
RSpec-tmbundlesearches forrspecin thevendor/gemsand thevendor/pluginsdirectories. Ifrspecis found,RSpec-tmbundledetermines the version to use based on the files present there. -
If no version is configured and no rspec directory could be found in vendor, then
RSpec-tmbundleattempts to run rspec-2 with:require 'rspec/core'
If that raises an exception, RSpec-tmbundle makes a final
attempt by trying to run rspec-1 with:
require 'spec/autorun'
The effectiveness of each approach is partially dependent on how
you manage your gem environment. The simplest (and suggested)
approach is to first just see if it just works, and if not, then
configure the version you want in the .rspec-tm file.
The RSpec TextMate bundle does not require "rubygems" so that
users who choose other packaging mechanisms can still use it. If
you are using Rubygems as your package manager, then the
simplest thing to do is
- open the TextMate Preferences
- go to the
Advancedtab - add a variable named
RUBYOPTwith the valuerubygems
You can set the following options in an .rspec-tm file in the
root directory of your project:
see RSpec-version, above.
Use Bundler, even if there is no Gemfile (in which case you
should have the BUNDLER_GEMFILE environment variable set).
Don't use Bundler, even if there is a Gemfile.
In addition to the standard TextMate shell variables, the RSpec TextMate bundle supports the following:
Set a custom formatter other than RSpec's TextMate formatter. Use
the full classname, e.g. 'Spec::Core::Formatters::WebKit'
Use this to set RSpec options just as you would in an .rspec
file.
If you're hacking on rspec yourself, point this to the
rspec-core project directory for rspec-2, or the rspec
directory for rspec-1.
There are lots of ways to configure TextMate to work with rvm,
but this is the one the we recommend:
First, copy the following into ~/.rvm/bin/textmate_ruby
#!/usr/bin/env sh
source ~/.rvm/scripts/rvm
cd .
exec ruby "$@"
Next, set up a TM_RUBY option in
TextMate/Preferences/Advanced/Shell Variables that points to the
textmate_ruby command.
Learn more at:
- http://beginrescueend.com/integration/textmate/
- http://groups.google.com/group/rubyversionmanager/browse_thread/thread/64b84bbcdf49e9b?fwc=1&pli=1
Parts of RSpec.tmbundle are based on Florian Weber's TDDMate.
The license of RSpec.tmbundle is the same as
RSpec's.