Closed baversjo closed 12 years ago
It seems more to be an issue with the Guard Interactor.
Try to add:
platform :ruby do
gem 'rb-readline'
end
to your Gemfile or to disable the interactor with the -i
/--no-interactions
option.
adding that gem worked great, thanks so much!
Great, you're welcome!
Hello! If I make a change to a rails model and then hit enter in the terminal to run all specs nothing happens. I've tried waiting for up to a minute. Looks like guard/spork is locked. After waiting, if I save the model file again my previous request to run all specs instantly starts successfully. If I do not change any "rails classes", running specs by hitting enter always works.
I just changed config.cache_classes to false in my test environment, hoping that was the cause but nothing changed in the behavior after restarting guard.
Here's my Guardfile (I followed the railscasts.com screencast on spork):
spec_helper.rb:
gem versions: spork (0.9.1) guard (1.0.2) guard-rspec (0.7.0) guard-spork (0.7.1) rails (3.2.3) rb-fsevent (0.9.1)