rspec users - Jun 2008 - Why has the --color gone from my life?

Hi all,
Running on OSX 10.5.3, Latest Rspec trunk, Rspec rails trunk, latest
autotest gem and rails 2.1

I''ve lost my colour output in autotest.

rake spec gives colour output, but autotest gives me black and white.

It was working a little bit before, I think I upgraded to the latest
versions of everything to get all the textmate snippets talking and being
friendly to one another again after I upgraded Ruby from the shipped 111
patch level to 114.

Not mission critical, but annoying :)

I mean... without it, you can only aim for "All specs grey!" which
doesn''t
quite sound as good.

Anyone have any pointers?

Mikel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20080604/603de80b/attachment.html>

This was an error, but I thought it was corrected by D. Chelimsky.

Check this topic:
http://www.ruby-forum.com/topic/154595

Juanma Cervera


-- 
Posted via http://www.ruby-forum.com/.

On Jun 6, 2008, at 10:57 AM, Juanma Cervera wrote:
> This was an error, but I thought it was corrected by D. Chelimsky.
That is correct - at least temporarily - there is a conflict with how  
rspec and autotest output to a terminal that makes it challenging for  
rspec to color code terminal output while not including the color code  
chars in html output.

If anybody is interested in helping to solve that, check out
http://rspec.lighthouseapp.com/projects/5645/tickets/413
.

Cheers,
David

This was fixed up updating to trunk:
3b76fda..befd422  master     -> origin/master

I now get colour, thanks all!

Mikel

On Sat, Jun 7, 2008 at 2:09 AM, David Chelimsky <dchelimsky at gmail.com>
wrote:
> On Jun 6, 2008, at 10:57 AM, Juanma Cervera wrote:
>
>  This was an error, but I thought it was corrected by D. Chelimsky.
>>
>
> That is correct - at least temporarily - there is a conflict with how rspec
> and autotest output to a terminal that makes it challenging for rspec to
> color code terminal output while not including the color code chars in html
> output.
>
> If anybody is interested in helping to solve that, check out
> http://rspec.lighthouseapp.com/projects/5645/tickets/413.
>
> Cheers,
> David
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20080610/50125cc2/attachment.html>

On 10 jun 2008, at 07:05, Mikel Lindsaar wrote:
> This was fixed up updating to trunk:
>
> 3b76fda..befd422  master     -> origin/master
Looks like I have the same problem now. Created a new rails app  
(2.1.0), and using the install instructions on the github wiki, leaves  
me with an autotest (ZenTest version 3.10.0) running autotest/rails  
instead of autotest/rails_rspec as some of my older projects do.
When I copy vendor/plugins/rspec-rails/lib/autotest/rails_rspec.rb to  
~/.autotest, autotest runs with:

/opt/local/bin/ruby -I.:lib:test -rtest/unit -e "%w[spec/controllers/ 
foos_routing_spec.rb spec/views/foos/index.html.erb_spec.rb spec/ 
helpers/foos_helper_spec.rb spec/models/foo_spec.rb spec/views/foos/ 
new.html.erb_spec.rb spec/views/foos/show.html.erb_spec.rb spec/views/ 
foos/edit.html.erb_spec.rb spec/controllers/ 
foos_controller_spec.rb].each { |f| require f }" | unit_diff -u

giving me grey specs.

So, without an .autotest, nothing at all happens. Running autotest -v  
gives, among all the .git files even Dunno! app/controllers/ 
application.rb!
With rspec-rails'' autotest, it runs with -r test/unit.

Weird stuff, hopefully someone makes sense of this al.
bartz

> On Sat, Jun 7, 2008 at 2:09 AM, David Chelimsky  
> <dchelimsky at gmail.com> wrote:
> On Jun 6, 2008, at 10:57 AM, Juanma Cervera wrote:
>
> This was an error, but I thought it was corrected by D. Chelimsky.
>
> That is correct - at least temporarily - there is a conflict with  
> how rspec and autotest output to a terminal that makes it  
> challenging for rspec to color code terminal output while not  
> including the color code chars in html output.
>
> If anybody is interested in helping to solve that, check out
http://rspec.lighthouseapp.com/projects/5645/tickets/413
> .
>
> Cheers,
> David
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

On Jul 8, 2008, at 2:09 PM, Bart Zonneveld wrote:
> On 10 jun 2008, at 07:05, Mikel Lindsaar wrote:
>
>> This was fixed up updating to trunk:
>>
>> 3b76fda..befd422  master     -> origin/master
>
> Looks like I have the same problem now. Created a new rails app  
> (2.1.0), and using the install instructions on the github wiki,  
> leaves me with an autotest (ZenTest version 3.10.0) running autotest/ 
> rails instead of autotest/rails_rspec as some of my older projects do.
> When I copy vendor/plugins/rspec-rails/lib/autotest/rails_rspec.rb  
> to ~/.autotest, autotest runs with:
Why are you copying that there?

Try doing this:

cd vendor/plugins/rspec
rake gem
rake install_gem
rake clobber
cd ../../../
autospec

Since you''re using edge, autospec is the new command to run autotest  
with rspec.

>
>
> /opt/local/bin/ruby -I.:lib:test -rtest/unit -e "%w[spec/controllers/ 
> foos_routing_spec.rb spec/views/foos/index.html.erb_spec.rb spec/ 
> helpers/foos_helper_spec.rb spec/models/foo_spec.rb spec/views/foos/ 
> new.html.erb_spec.rb spec/views/foos/show.html.erb_spec.rb spec/ 
> views/foos/edit.html.erb_spec.rb spec/controllers/ 
> foos_controller_spec.rb].each { |f| require f }" | unit_diff -u
>
> giving me grey specs.
>
> So, without an .autotest, nothing at all happens. Running autotest - 
> v gives, among all the .git files even Dunno! app/controllers/ 
> application.rb!
> With rspec-rails'' autotest, it runs with -r test/unit.
>
> Weird stuff, hopefully someone makes sense of this al.
> bartz
>
>
>> On Sat, Jun 7, 2008 at 2:09 AM, David Chelimsky  
>> <dchelimsky at gmail.com> wrote:
>> On Jun 6, 2008, at 10:57 AM, Juanma Cervera wrote:
>>
>> This was an error, but I thought it was corrected by D. Chelimsky.
>>
>> That is correct - at least temporarily - there is a conflict with  
>> how rspec and autotest output to a terminal that makes it  
>> challenging for rspec to color code terminal output while not  
>> including the color code chars in html output.
>>
>> If anybody is interested in helping to solve that, check out
http://rspec.lighthouseapp.com/projects/5645/tickets/413
>> .
>>
>> Cheers,
>> David
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

On 8 jul 2008, at 21:43, David Chelimsky wrote:
> On Jul 8, 2008, at 2:09 PM, Bart Zonneveld wrote:
>
>> On 10 jun 2008, at 07:05, Mikel Lindsaar wrote:
>>
>>> This was fixed up updating to trunk:
>>>
>>> 3b76fda..befd422  master     -> origin/master
>>
>> Looks like I have the same problem now. Created a new rails app  
>> (2.1.0), and using the install instructions on the github wiki,  
>> leaves me with an autotest (ZenTest version 3.10.0) running  
>> autotest/rails instead of autotest/rails_rspec as some of my older  
>> projects do.
>> When I copy vendor/plugins/rspec-rails/lib/autotest/rails_rspec.rb  
>> to ~/.autotest, autotest runs with:
>
> Why are you copying that there?
Just trying whatever I could think of :).
> Try doing this:
>
> cd vendor/plugins/rspec
> rake gem
> rake install_gem
> rake clobber
> cd ../../../
> autospec
>
> Since you''re using edge, autospec is the new command to run
autotest
> with rspec.
Okay, thanks. Might be worth it to actually write this somewhere down,  
such as on the wiki?
This is nowhere to be found.

thanks,
bartz

>> /opt/local/bin/ruby -I.:lib:test -rtest/unit -e "%w[spec/ 
>> controllers/foos_routing_spec.rb spec/views/foos/ 
>> index.html.erb_spec.rb spec/helpers/foos_helper_spec.rb spec/models/ 
>> foo_spec.rb spec/views/foos/new.html.erb_spec.rb spec/views/foos/ 
>> show.html.erb_spec.rb spec/views/foos/edit.html.erb_spec.rb spec/ 
>> controllers/foos_controller_spec.rb].each { |f| require f }" |  
>> unit_diff -u
>>
>> giving me grey specs.
>>
>> So, without an .autotest, nothing at all happens. Running autotest - 
>> v gives, among all the .git files even Dunno! app/controllers/ 
>> application.rb!
>> With rspec-rails'' autotest, it runs with -r test/unit.
>>
>> Weird stuff, hopefully someone makes sense of this al.
>> bartz
>>
>>
>>> On Sat, Jun 7, 2008 at 2:09 AM, David Chelimsky <dchelimsky at
gmail.com
>>> > wrote:
>>> On Jun 6, 2008, at 10:57 AM, Juanma Cervera wrote:
>>>
>>> This was an error, but I thought it was corrected by D. Chelimsky.
>>>
>>> That is correct - at least temporarily - there is a conflict with  
>>> how rspec and autotest output to a terminal that makes it  
>>> challenging for rspec to color code terminal output while not  
>>> including the color code chars in html output.
>>>
>>> If anybody is interested in helping to solve that, check out
http://rspec.lighthouseapp.com/projects/5645/tickets/413
>>> .
>>>
>>> Cheers,
>>> David
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

On Jul 8, 2008, at 2:52 PM, Bart Zonneveld wrote:
>
> On 8 jul 2008, at 21:43, David Chelimsky wrote:
>
>> On Jul 8, 2008, at 2:09 PM, Bart Zonneveld wrote:
>>
>>> On 10 jun 2008, at 07:05, Mikel Lindsaar wrote:
>>>
>>>> This was fixed up updating to trunk:
>>>>
>>>> 3b76fda..befd422  master     -> origin/master
>>>
>>> Looks like I have the same problem now. Created a new rails app  
>>> (2.1.0), and using the install instructions on the github wiki,  
>>> leaves me with an autotest (ZenTest version 3.10.0) running  
>>> autotest/rails instead of autotest/rails_rspec as some of my older
>>> projects do.
>>> When I copy vendor/plugins/rspec-rails/lib/autotest/rails_rspec.rb
>>> to ~/.autotest, autotest runs with:
>>
>> Why are you copying that there?
>
> Just trying whatever I could think of :).
>
>> Try doing this:
>>
>> cd vendor/plugins/rspec
>> rake gem
>> rake install_gem
>> rake clobber
>> cd ../../../
>> autospec
>>
>> Since you''re using edge, autospec is the new command to run  
>> autotest with rspec.
>
> Okay, thanks. Might be worth it to actually write this somewhere  
> down, such as on the wiki?
> This is nowhere to be found.
http://github.com/dchelimsky/rspec/tree/master/History.txt

Cheers,
David
> thanks,
> bartz
>
>
>>> /opt/local/bin/ruby -I.:lib:test -rtest/unit -e "%w[spec/ 
>>> controllers/foos_routing_spec.rb spec/views/foos/ 
>>> index.html.erb_spec.rb spec/helpers/foos_helper_spec.rb spec/ 
>>> models/foo_spec.rb spec/views/foos/new.html.erb_spec.rb spec/views/
>>> foos/show.html.erb_spec.rb spec/views/foos/edit.html.erb_spec.rb  
>>> spec/controllers/foos_controller_spec.rb].each { |f| require f
}"
>>> | unit_diff -u
>>>
>>> giving me grey specs.
>>>
>>> So, without an .autotest, nothing at all happens. Running autotest
>>> -v gives, among all the .git files even Dunno! app/controllers/ 
>>> application.rb!
>>> With rspec-rails'' autotest, it runs with -r test/unit.
>>>
>>> Weird stuff, hopefully someone makes sense of this al.
>>> bartz
>>>
>>>
>>>> On Sat, Jun 7, 2008 at 2:09 AM, David Chelimsky <dchelimsky
at gmail.com
>>>> > wrote:
>>>> On Jun 6, 2008, at 10:57 AM, Juanma Cervera wrote:
>>>>
>>>> This was an error, but I thought it was corrected by D.
Chelimsky.
>>>>
>>>> That is correct - at least temporarily - there is a conflict
with
>>>> how rspec and autotest output to a terminal that makes it  
>>>> challenging for rspec to color code terminal output while not  
>>>> including the color code chars in html output.
>>>>
>>>> If anybody is interested in helping to solve that, check out
http://rspec.lighthouseapp.com/projects/5645/tickets/413
>>>> .
>>>>
>>>> Cheers,
>>>> David
>>>>
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

On Jul 8, 2008, at 2:55 PM, David Chelimsky wrote:
> On Jul 8, 2008, at 2:52 PM, Bart Zonneveld wrote:
>
>>
>> On 8 jul 2008, at 21:43, David Chelimsky wrote:
>>
>>> On Jul 8, 2008, at 2:09 PM, Bart Zonneveld wrote:
>>>
>>>> On 10 jun 2008, at 07:05, Mikel Lindsaar wrote:
>>>>
>>>>> This was fixed up updating to trunk:
>>>>>
>>>>> 3b76fda..befd422  master     -> origin/master
>>>>
>>>> Looks like I have the same problem now. Created a new rails app
>>>> (2.1.0), and using the install instructions on the github wiki,
>>>> leaves me with an autotest (ZenTest version 3.10.0) running  
>>>> autotest/rails instead of autotest/rails_rspec as some of my  
>>>> older projects do.
>>>> When I copy vendor/plugins/rspec-rails/lib/autotest/ 
>>>> rails_rspec.rb to ~/.autotest, autotest runs with:
>>>
>>> Why are you copying that there?
>>
>> Just trying whatever I could think of :).
>>
>>> Try doing this:
>>>
>>> cd vendor/plugins/rspec
>>> rake gem
>>> rake install_gem
>>> rake clobber
>>> cd ../../../
>>> autospec
>>>
>>> Since you''re using edge, autospec is the new command to
run
>>> autotest with rspec.
>>
>> Okay, thanks. Might be worth it to actually write this somewhere  
>> down, such as on the wiki?
>> This is nowhere to be found.
>
> http://github.com/dchelimsky/rspec/tree/master/History.txt
Just added ''script/autospec'' (in rspec-rails) too -
http://github.com/dchelimsky/rspec-rails/tree/master/History.txt

Cheers,
David
>
>
> Cheers,
> David
>
>> thanks,
>> bartz
>>
>>
>>>> /opt/local/bin/ruby -I.:lib:test -rtest/unit -e "%w[spec/ 
>>>> controllers/foos_routing_spec.rb spec/views/foos/ 
>>>> index.html.erb_spec.rb spec/helpers/foos_helper_spec.rb spec/ 
>>>> models/foo_spec.rb spec/views/foos/new.html.erb_spec.rb spec/ 
>>>> views/foos/show.html.erb_spec.rb spec/views/foos/ 
>>>> edit.html.erb_spec.rb spec/controllers/ 
>>>> foos_controller_spec.rb].each { |f| require f }" |
unit_diff -u
>>>>
>>>> giving me grey specs.
>>>>
>>>> So, without an .autotest, nothing at all happens. Running  
>>>> autotest -v gives, among all the .git files even Dunno! app/ 
>>>> controllers/application.rb!
>>>> With rspec-rails'' autotest, it runs with -r test/unit.
>>>>
>>>> Weird stuff, hopefully someone makes sense of this al.
>>>> bartz
>>>>
>>>>
>>>>> On Sat, Jun 7, 2008 at 2:09 AM, David Chelimsky
<dchelimsky at gmail.com
>>>>> > wrote:
>>>>> On Jun 6, 2008, at 10:57 AM, Juanma Cervera wrote:
>>>>>
>>>>> This was an error, but I thought it was corrected by D.
Chelimsky.
>>>>>
>>>>> That is correct - at least temporarily - there is a
conflict
>>>>> with how rspec and autotest output to a terminal that makes
it
>>>>> challenging for rspec to color code terminal output while
not
>>>>> including the color code chars in html output.
>>>>>
>>>>> If anybody is interested in helping to solve that, check
out http://rspec.lighthouseapp.com/projects/5645/tickets/413
>>>>> .
>>>>>
>>>>> Cheers,
>>>>> David
>>>>>
>>>>> _______________________________________________
>>>>> rspec-users mailing list
>>>>> rspec-users at rubyforge.org
>>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>>
>>>>> _______________________________________________
>>>>> rspec-users mailing list
>>>>> rspec-users at rubyforge.org
>>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>