On Sat, Aug 25, 2012 at 10:01 AM, cat123 <[email protected]> wrote: > $ bundle exec rspec spec/requests/user_pages_spec.rb / > > I had accidentally used / instead of \ and when I hit enter to > continue my command I suddenly found myself in 'no man's land' with no > command prompt of any kind. I couldn't get out of it --tried Cntrl+c, > Cntrol+d, q, exit-- nothing worked. So I just shut the window and went back > in. Would this have caused some issue? What would / do (instead of \ )? > Otherwise, I have no idea why this could be happening...
passing "/" in to rspec would tell it "go check every single directory on all your disks for files ending in _spec.rb". No wonder it froze. What OS were you on? On Unix (including Mac OS X) you can use this trick to kill hung processes: - control-Z - kill % (then if that doesn't work) - kill -9 % Note also that closing a window doesn't always kill the process running in that window. Use "ps" to see all (or some) of your processes you launched from a terminal and see if it's there. I don't know if that caused your other problem, but I doubt it. Sounds like a classic Rails config issue to me. Check your config/databases.yml and so forth. -- Alex Chaffee - [email protected] http://alexchaffee.com http://twitter.com/alexch -- You received this message because you are subscribed to the Google Groups "rspec" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
