> rspec, not rake:
Oops! I missed that.. So other than this debugger thing, are there any other
differences between rake spec and rspec spec?
Patrick J. Collins
http://collinatorstudios.com
___
rspec-users mailing list
rspec-users@rubyforge.org
http:/
On Jun 6, 2011, at 7:53 PM, Patrick J. Collins wrote:
>> rake doesn't take arguments like that. Try 'rspec spec --debugger'.
> Hmm, that gives no output at all.. I just get a bash prompt immediately
> after entering 'rake spec --debugger'
rspec, not rake:
rspec spec --debugger
_
> rake doesn't take arguments like that. Try 'rspec spec --debugger'.
Hmm, that gives no output at all.. I just get a bash prompt immediately
after entering 'rake spec --debugger'
Patrick J. Collins
http://collinatorstudios.com
___
rspec-users mailing l
On Jun 6, 2011, at 6:49 PM, Patrick J. Collins wrote:
>> Here's how I deal with this:
>>
>> bundle install --binstubs # installs bin/rake, etc
>> export PATH=./bin:$PATH
>
> Great! What about using debugger?
>
> rake spec gives me:
> "* debugger statement ignored, use -d or --debug o
> Here's how I deal with this:
>
> bundle install --binstubs # installs bin/rake, etc
> export PATH=./bin:$PATH
Great! What about using debugger?
rake spec gives me:
"* debugger statement ignored, use -d or --debug option to enable
debugging"
rake spec -d gives me:
"ambigu
On Jun 6, 2011, at 4:26 PM, Patrick J. Collins wrote:
> Hi everyone,
>
> I am using rvm, and when I try to do rake spec, I get:
>
> "You have already activated rake 0.9.0, but your Gemfile requires rake
> 0.8.7.
> Consider using bundle exec."
>
> ... Is there a way to get around t
Hi everyone,
I am using rvm, and when I try to do rake spec, I get:
"You have already activated rake 0.9.0, but your Gemfile requires rake
0.8.7.
Consider using bundle exec."
... Is there a way to get around this so I don't have to do bundle exec rake
spec each and every time?
