On Jan 21, 2008 6:53 PM, BenFyvie <[EMAIL PROTECTED]> wrote: > > I am using Rspec 1.1.2 on Windows XP SP2 > > I am receiving the following error when I run 'rake spec' from a brand new > project: > C:/SVN_Projects/rspec/vendor/plugins/rspec/lib/spec/runner/options.rb:107:in > `colour=': You must gem install win32console to use colour on Windows > (RuntimeError) > > I have the win32console gem installed and the error still occurs. It seems > that the require statement in options.rb line 105 is throwing an exception > and I am not sure why. I have even gone to the extent of replacing > 'Win32/Console/ANSI' with the absolute path to the ANSI file and still no > luck. When I run the require statement in a console everything works fine > and dandy. > > Now if I remove the --colour option from the spec.opts file then it doesn't > need the win32console gem; however, I then receive this error: > C:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:100:in > `const_missing': uninitialized constant Spec::Rails (NameError) > > I do have the rspec_on_rails plugin installed. Can anyone offer me any > suggestions on how to troubleshoot this issue? Thanks in advance!
I'll be looking into this tonight, since I already reported that, but using rake and spec command only: http://rspec.lighthouseapp.com/projects/5645/tickets/244-no-coloured-output-on-windows-due-missing-rubyopt It seems that --colour affects not only lib/runner/options.rb, but other places too. Maybe we should change the behavior for windows and revert to false if Win32/Console/ANSI is not found instead of raising a exception. David, Aslak? -- Luis Lavena Multimedia systems - A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. Douglas Adams _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
