Jeff, always a good idea -- it didn't work in this case, but I've seen it before. I ended up uninstalling my rails gem (and the action* gems) and reinstalling; then, reinstalling rspec and rspec-rails. After that, rspec worked without the issues I'd seen before. Don't know why. Thanks.
On Mon, Apr 13, 2009 at 3:19 PM, Jeff Talbot <[email protected]>wrote: > I'm sure you have tried this, but it's such a simple step that I'll throw > it out. > > I've had a couple instances in the past where gems were not being loaded > and after troubleshooting for a while, I found that all problems were > magically solved by firing up a new instance of my shell (new terminal > window). Somehow the environment had gotten confused.... > > Worth a shot. > > Jeff > > On Mon, Apr 13, 2009 at 3:04 PM, Sarah Gray <[email protected]> wrote: > >> When uninstalling rspec, should you: >> >> Remove executables: >> autospec, spec >> in addition to the gem? [Yn] >> >> And, is there possible fallout from doing this step wrong? >> >> >> >> On Mon, Apr 13, 2009 at 2:48 PM, David Chelimsky <[email protected]>wrote: >> >>> On Mon, Apr 13, 2009 at 4:34 PM, Sarah Gray <[email protected]> >>> wrote: >>> > rails -v >>> > 2.3.2 >>> >>> Me too. Not sure what to tell you. >>> >>> Anybody else? >>> >>> >> >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users > -- http://www.fabled.net/blog/
_______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
