On Jun 22, 2010, at 2:09 AM, rogerdpack wrote: >>> The skinny of this request is that I'd find it more useful to actually >>> have the code displayed that failed on line 14, in this case, the word >>> "fail" > ... >> Already done in rspec-2. Likely won't backport it to rspec-1 for some time >> (if ever). > > Nice. Looks like rspec-2 will fit the bill for me for now, then. > > 1) Gem speeding Gem.bin_path the fake sick way should fake guess the > right path instead of loading full rubygems for now > Failure/Error: Unable to find matching line from backtrace > # spec.faster_rubygems.rb:29 > # spec.faster_rubygems.rb:13 > > Perhaps it isn't quite windows friendly?
That happens now and then when the error is in code generated with eval(string) with no file and ref numbers. Has nothing to do with Windows as far as I know, and is the same problem we have with ruby-debug. HTH, David _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
