# Iron-term-ansicolor 0.0.2 Released **URL:** \ **Category:** IronRuby\ **Created:** [February 27, 2010, 5:16am UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249 "2010-02-27T05:16:45Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [February 27, 2010, 5:16am UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/1 "2010-02-27T05:16:45Z")
Tonight, I released an update to iron-term-ansicolor, a library for IronRuby that provides console colors for apps like RSpec and Cucumber (Cucumber already makes use of this, and I bet it would not be too much trouble to add to RSpec). [http://rubygems.org/gems/iron-term-ansicolor](http://rubygems.org/gems/iron-term-ansicolor) [http://rubygems.org/gems/iron-term-ansicolor](http://rubygems.org/gems/iron-term-ansicolor)igem install iron-term-ansicolor The source is available on github: > **[GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using...](https://github.com/hotgazpacho/iron-term-ansicolor)** > > term-ansicolor for IronRuby using .Net framework libraries - GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using .Net framework libraries Big thanks to Danny Coates for devising a much better way to parse the ANSI control codes! ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 7:20am UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/2 "2010-03-01T07:20:40Z")
Very cool! So if a user runs Cucumber on IronRuby, does Cucumber give the right error message about having to install iron-term-ansicolor? Cucumber used to say that you had to install win32console. Just checking that iron-term-ansicolor will be easily discoverable. From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Friday, February 26, 2010 8:15 PM To: ironruby-core Subject: [Ironruby-core] iron-term-ansicolor 0.0.2 Released Tonight, I released an update to iron-term-ansicolor, a library for IronRuby that provides console colors for apps like RSpec and Cucumber (Cucumber already makes use of this, and I bet it would not be too much trouble to add to RSpec). [http://rubygems.org/gems/iron-term-ansicolor](http://rubygems.org/gems/iron-term-ansicolor) igem install iron-term-ansicolor The source is available on github: > **[GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using...](https://github.com/hotgazpacho/iron-term-ansicolor)** > > term-ansicolor for IronRuby using .Net framework libraries - GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using .Net framework libraries Big thanks to Danny Coates for devising a much better way to parse the ANSI control codes! – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 7:36pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/3 "2010-03-01T19:36:59Z")
Yes, Aslak accepted a patch to Cucumber from me many months ago when I released 0.0.1. ## Right near the top of lib/cucumber/formatter/ansicolor.rb[http://github.com/hotgazpacho/cucumber/commit/abeaf62d2e7c9dd576a27365cdaa29aa6067547c#diff-0](http://github.com/hotgazpacho/cucumber/commit/abeaf62d2e7c9dd576a27365cdaa29aa6067547c#diff-0) [http://github.com/hotgazpacho/cucumber/commit/abeaf62d2e7c9dd576a27365cdaa29aa6067547c#diff-0](http://github.com/hotgazpacho/cucumber/commit/abeaf62d2e7c9dd576a27365cdaa29aa6067547c#diff-0) Will G. > **[hotgazpacho](http://hotgazpacho.org/)** ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 7:07pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/4 "2010-03-01T19:07:08Z")
Having issues installing this with ironruby rc2. Anyone else seeing that? I tried running: ir -S gem install cucumber iron-term-ansicolor Pasted output: [20] » ir -v -e ‘exit’ IronRuby 0.9.4.0 on .NET 2.0.50727.4927 C:\temp [21] » ir -S gem install cucumber iron-term-ansicolor (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 ``` (::) U P G R A D I N G (::) ``` Thank you for installing cucumber-0.6.2. Please be sure to read [http://wiki.github.com/aslakhellesoy/cucumber/upgrading](http://wiki.github.com/aslakhellesoy/cucumber/upgrading) for important information about this release. Happy cuking! (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 Successfully installed term-ansicolor-1.0.4 Successfully installed polyglot-0.3.0 Successfully installed treetop-1.4.4 Successfully installed builder-2.1.2 Successfully installed diff-lcs-1.1.2 Successfully installed json\_pure-1.2.2 Successfully installed cucumber-0.6.2 ERROR: While executing gem … (IndexError) Index was outside the bounds of the array. C:\temp [22] » ir -S gem install iron-term-ansicolor ERROR: While executing gem … (IndexError) Index was outside the bounds of the array. C:\temp [23] » JD From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Shri B. Sent: Sunday, February 28, 2010 10:20 PM To: removed\_email\_address@domain.invalid Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released Very cool! So if a user runs Cucumber on IronRuby, does Cucumber give the right error message about having to install iron-term-ansicolor? Cucumber used to say that you had to install win32console. Just checking that iron-term-ansicolor will be easily discoverable. From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Friday, February 26, 2010 8:15 PM To: ironruby-core Subject: [Ironruby-core] iron-term-ansicolor 0.0.2 Released Tonight, I released an update to iron-term-ansicolor, a library for IronRuby that provides console colors for apps like RSpec and Cucumber (Cucumber already makes use of this, and I bet it would not be too much trouble to add to RSpec). [http://rubygems.org/gems/iron-term-ansicolor](http://rubygems.org/gems/iron-term-ansicolor) igem install iron-term-ansicolor The source is available on github: > **[GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using...](https://github.com/hotgazpacho/iron-term-ansicolor)** > > term-ansicolor for IronRuby using .Net framework libraries - GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using .Net framework libraries Big thanks to Danny Coates for devising a much better way to parse the ANSI control codes! – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 7:38pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/5 "2010-03-01T19:38:44Z")
I am seeing this error, too ☹ I can install locally. Perhaps it is a problem with the Gem sources? C:\Users\will.green\dev\iron-term-ansicolor\pkg\>ir -S gem install iron-term-ansicolor-0.0.2.gem Successfully installed iron-term-ansicolor-0.0.2 1 gem installed Installing ri documentation for iron-term-ansicolor-0.0.2… unrecognized option `–format’ For help on options, try ‘rdoc --help’ – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 7:41pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/6 "2010-03-01T19:41:05Z")
C:\Users\jdeville\projects\cucumber [35] » ir -S gem sources \*\*\* CURRENT SOURCES \*\*\* [http://gemcutter.org](http://gemcutter.org) [http://gems.rubyforge.org/](http://gems.rubyforge.org/) [http://gems.github.com](http://gems.github.com) That’s what I have for sources, fyi. I’ll try to look into it more later if no one else does. JD From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Monday, March 01, 2010 10:34 AM To: removed\_email\_address@domain.invalid Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released I am seeing this error, too ☹ I can install locally. Perhaps it is a problem with the Gem sources? C:\Users\will.green\dev\iron-term-ansicolor\pkg\>ir -S gem install iron-term-ansicolor-0.0.2.gem Successfully installed iron-term-ansicolor-0.0.2 1 gem installed Installing ri documentation for iron-term-ansicolor-0.0.2… unrecognized option `–format’ For help on options, try ‘rdoc --help’ – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) On Mon, Mar 1, 2010 at 1:04 PM, Jim D. \ wrote: Having issues installing this with ironruby rc2. Anyone else seeing that? I tried running: ir -S gem install cucumber iron-term-ansicolor Pasted output: [20] » ir -v -e ‘exit’ IronRuby 0.9.4.0 on .NET 2.0.50727.4927 C:\temp [21] » ir -S gem install cucumber iron-term-ansicolor (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 ``` (::) U P G R A D I N G (::) ``` Thank you for installing cucumber-0.6.2. Please be sure to read [http://wiki.github.com/aslakhellesoy/cucumber/upgrading](http://wiki.github.com/aslakhellesoy/cucumber/upgrading) for important information about this release. Happy cuking! (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 Successfully installed term-ansicolor-1.0.4 Successfully installed polyglot-0.3.0 Successfully installed treetop-1.4.4 Successfully installed builder-2.1.2 Successfully installed diff-lcs-1.1.2 Successfully installed json\_pure-1.2.2 Successfully installed cucumber-0.6.2 ERROR: While executing gem … (IndexError) Index was outside the bounds of the array. C:\temp [22] » ir -S gem install iron-term-ansicolor ERROR: While executing gem … (IndexError) Index was outside the bounds of the array. C:\temp [23] » JD From: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Shri B. Sent: Sunday, February 28, 2010 10:20 PM To: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released Very cool! So if a user runs Cucumber on IronRuby, does Cucumber give the right error message about having to install iron-term-ansicolor? Cucumber used to say that you had to install win32console. Just checking that iron-term-ansicolor will be easily discoverable. From: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Friday, February 26, 2010 8:15 PM To: ironruby-core Subject: [Ironruby-core] iron-term-ansicolor 0.0.2 Released Tonight, I released an update to iron-term-ansicolor, a library for IronRuby that provides console colors for apps like RSpec and Cucumber (Cucumber already makes use of this, and I bet it would not be too much trouble to add to RSpec). [http://rubygems.org/gems/iron-term-ansicolor](http://rubygems.org/gems/iron-term-ansicolor) igem install iron-term-ansicolor The source is available on github: > **[GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using...](https://github.com/hotgazpacho/iron-term-ansicolor)** > > term-ansicolor for IronRuby using .Net framework libraries - GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using .Net framework libraries Big thanks to Danny Coates for devising a much better way to parse the ANSI control codes! – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) * * * Ironruby-core mailing list removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 7:43pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/7 "2010-03-01T19:43:26Z")
Or, possibly related to version of RubyGems (1.3.5) shipped with IronRuby RC2. Latest is 1.3.6 Sadly, I cannot run ir -S gem update --system: C:\Users\will.green\dev\iron-term-ansicolor\>ir -S gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.6 Updating RubyGems to 1.3.6 Installing RubyGems 1.3.6 ERROR: While executing gem … (Gem::Exception) [BUG] invalid exec\_format “ir”, no %s – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 7:45pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/8 "2010-03-01T19:45:11Z")
## I also get it when I try to install from a remote location. But downloading the source and building the gem does work. Met vriendelijke groeten - Best regards - Salutations Ivan Porto C. Web: [http://whiterabbitconsulting.eu](http://whiterabbitconsulting.eu) - [http://flanders.co.nz](http://flanders.co.nz) Twitter: [http://twitter.com/casualjim](http://twitter.com/casualjim) Author of IronRuby in Action ([IronRuby in Action - Ivan Porto Carrero and Adam Burmister | Manning](http://manning.com/carrero)) Microsoft IronRuby/C# MVP ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 8:06pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/9 "2010-03-01T20:06:51Z")
As a temporary workaround, I’ve uploaded the gem to the downloads section for the project: [http://github.com/hotgazpacho/iron-term-ansicolor/downloads](http://github.com/hotgazpacho/iron-term-ansicolor/downloads) Simply download, then, in the directory you downloaded to: ## ir -S gem install iron-term-ansicolor-0.0.2.gem [http://github.com/hotgazpacho/iron-term-ansicolor/downloads](http://github.com/hotgazpacho/iron-term-ansicolor/downloads) Will G. > **[hotgazpacho](http://hotgazpacho.org/)** On Mon, Mar 1, 2010 at 1:41 PM, Ivan Porto C. \< ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 8:24pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/10 "2010-03-01T20:24:25Z")
Thanks! From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Monday, March 01, 2010 10:55 AM To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released As a temporary workaround, I’ve uploaded the gem to the downloads section for the project: [http://github.com/hotgazpacho/iron-term-ansicolor/downloads](http://github.com/hotgazpacho/iron-term-ansicolor/downloads) Simply download, then, in the directory you downloaded to: ir -S gem install iron-term-ansicolor-0.0.2.gem – Will G. > **[hotgazpacho](http://hotgazpacho.org/)** ## On Mon, Mar 1, 2010 at 1:41 PM, Ivan Porto C. \<[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)\> wrote: I also get it when I try to install from a remote location. But downloading the source and building the gem does work. Met vriendelijke groeten - Best regards - Salutations Ivan Porto C. Web: [http://whiterabbitconsulting.eu](http://whiterabbitconsulting.eu) - [http://flanders.co.nz](http://flanders.co.nz) Twitter: [http://twitter.com/casualjim](http://twitter.com/casualjim) Author of IronRuby in Action ([IronRuby in Action - Ivan Porto Carrero and Adam Burmister | Manning](http://manning.com/carrero)) Microsoft IronRuby/C# MVP On Mon, Mar 1, 2010 at 7:39 PM, Jim D. \<[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)\> wrote: C:\Users\jdeville\projects\cucumber [35] » ir -S gem sources \*\*\* CURRENT SOURCES \*\*\* > **[RubyGems.org | your community gem host](https://rubygems.org)** > **[RubyGems.org | your community gem host](https://rubygems.org)** [http://gems.github.com](http://gems.github.com) That’s what I have for sources, fyi. I’ll try to look into it more later if no one else does. JD From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Monday, March 01, 2010 10:34 AM To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released I am seeing this error, too ☹ I can install locally. Perhaps it is a problem with the Gem sources? C:\Users\will.green\dev\iron-term-ansicolor\pkg\>ir -S gem install iron-term-ansicolor-0.0.2.gem Successfully installed iron-term-ansicolor-0.0.2 1 gem installed Installing ri documentation for iron-term-ansicolor-0.0.2… unrecognized option `–format’ For help on options, try ‘rdoc --help’ – Will G. > **[hotgazpacho](http://hotgazpacho.org/)** On Mon, Mar 1, 2010 at 1:04 PM, Jim D. \<[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)\> wrote: Having issues installing this with ironruby rc2. Anyone else seeing that? I tried running: ir -S gem install cucumber iron-term-ansicolor Pasted output: [20] » ir -v -e ‘exit’ IronRuby 0.9.4.0 on .NET 2.0.50727.4927 C:\temp [21] » ir -S gem install cucumber iron-term-ansicolor (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 ``` (::) U P G R A D I N G (::) ``` Thank you for installing cucumber-0.6.2. Please be sure to read [http://wiki.github.com/aslakhellesoy/cucumber/upgrading](http://wiki.github.com/aslakhellesoy/cucumber/upgrading) for important information about this release. Happy cuking! (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 (:🙂 Successfully installed term-ansicolor-1.0.4 Successfully installed polyglot-0.3.0 Successfully installed treetop-1.4.4 Successfully installed builder-2.1.2 Successfully installed diff-lcs-1.1.2 Successfully installed json\_pure-1.2.2 Successfully installed cucumber-0.6.2 ERROR: While executing gem … (IndexError) Index was outside the bounds of the array. C:\temp [22] » ir -S gem install iron-term-ansicolor ERROR: While executing gem … (IndexError) Index was outside the bounds of the array. C:\temp [23] » JD From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Shri B. Sent: Sunday, February 28, 2010 10:20 PM To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released Very cool! So if a user runs Cucumber on IronRuby, does Cucumber give the right error message about having to install iron-term-ansicolor? Cucumber used to say that you had to install win32console. Just checking that iron-term-ansicolor will be easily discoverable. From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Friday, February 26, 2010 8:15 PM To: ironruby-core Subject: [Ironruby-core] iron-term-ansicolor 0.0.2 Released Tonight, I released an update to iron-term-ansicolor, a library for IronRuby that provides console colors for apps like RSpec and Cucumber (Cucumber already makes use of this, and I bet it would not be too much trouble to add to RSpec). > **[iron-term-ansicolor | RubyGems.org | your community gem host](https://rubygems.org/gems/iron-term-ansicolor)** igem install iron-term-ansicolor The source is available on github: > **[GitHub - hotgazpacho/iron-term-ansicolor: term-ansicolor for IronRuby using .Net framework...](https://github.com/hotgazpacho/iron-term-ansicolor)** > > term-ansicolor for IronRuby using .Net framework libraries Big thanks to Danny Coates for devising a much better way to parse the ANSI control codes! – Will G. > **[hotgazpacho](http://hotgazpacho.org/)** * * * Ironruby-core mailing list [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) * * * Ironruby-core mailing list [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) * * * Ironruby-core mailing list [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 10:29pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/11 "2010-03-01T22:29:41Z")
I don’t see why not. That said, there has been no testing specifically to verify that. If you clone the git repo, install rake and rspec, and run rake, the default rake task is to run the rspec specifications. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 1, 2010, 9:49pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/12 "2010-03-01T21:49:52Z")
Can this gem be used with IronRuby rc 1. ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 2, 2010, 4:49pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/13 "2010-03-02T16:49:31Z")
I released iron-term-ansicolor 0.0.3 last night after testing the gem install locally first. Please let me know if you still have trouble installing it from [Rubygems.org](http://Rubygems.org). Also, I’ve submitted a patch to RSpec to use iron-term-ansicolor if it can, the same way it tries to use win32console under MRI. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 2, 2010, 5:48am UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/14 "2010-03-02T05:48:07Z")
I think I may have pushed a corrupted gem :-/ Sorry about that folks. Trying to get the bits in place to yank it from gemcutter and replace it with a known good version of the gem. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 2, 2010, 7:02pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/15 "2010-03-02T19:02:26Z")
This brings a question to mind - what should the general approach be for porting existing gems to IronRuby? There could be two possible approaches: 1. ``` Create a gem with the same name (“win32console” in this case), ``` and specify platform==”ironruby”. That way, dependent gems do not need to be updated, and users have to remember just one name. IronRuby will use the version with platform==”ironruby”, and MRI will use the one with platform==”mswin32”. So there should not be any clashes even if you use MRI and IronRuby on the same machine. 1. ``` Create a new gem like iron-term-ansicolor. ``` Any pro or cons to the two? What should the recommendation be in general? From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Tuesday, March 02, 2010 7:47 AM To: ironruby-core Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released I released iron-term-ansicolor 0.0.3 last night after testing the gem install locally first. Please let me know if you still have trouble installing it from [Rubygems.org](http://Rubygems.org). Also, I’ve submitted a patch to RSpec to use iron-term-ansicolor if it can, the same way it tries to use win32console under MRI. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 2, 2010, 9:00pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/16 "2010-03-02T21:00:07Z")
That all depends on how Gem checks the platform. If it uses the RUBY\_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 2, 2010, 7:10pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/17 "2010-03-02T19:10:03Z")
I believe JRuby is doing the 1st one, which makes sense in my opinion. If possible we should prefer platform == “ironruby”, (or .net, do we need to differentiate .net and mono?), but accept others. JD From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Shri B. Sent: Tuesday, March 02, 2010 10:02 AM To: removed\_email\_address@domain.invalid Subject: [Ironruby-core] IronRuby version of existing gems This brings a question to mind - what should the general approach be for porting existing gems to IronRuby? There could be two possible approaches: 1. ``` Create a gem with the same name (“win32console” in this case), ``` and specify platform==”ironruby”. That way, dependent gems do not need to be updated, and users have to remember just one name. IronRuby will use the version with platform==”ironruby”, and MRI will use the one with platform==”mswin32”. So there should not be any clashes even if you use MRI and IronRuby on the same machine. 1. ``` Create a new gem like iron-term-ansicolor. ``` Any pro or cons to the two? What should the recommendation be in general? From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Tuesday, March 02, 2010 7:47 AM To: ironruby-core Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released I released iron-term-ansicolor 0.0.3 last night after testing the gem install locally first. Please let me know if you still have trouble installing it from [Rubygems.org](http://Rubygems.org). Also, I’ve submitted a patch to RSpec to use iron-term-ansicolor if it can, the same way it tries to use win32console under MRI. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 3, 2010, 6:56pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/18 "2010-03-03T18:56:01Z")
It does seem like there isn’t a way to distinguish between IronRuby and MRI. C:\> ir.exe > > > require “rubygems” > > > =\> true > > > Gem::Platform.local() > > > =\> #\ JRuby otoh does seem to do something different C:\> jruby.exe irb(main):001:0\> require “rubygems” =\> true irb(main):002:0\> Gem::Platform.local() =\> #\ From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Tuesday, March 02, 2010 11:52 AM To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: Re: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses the RUBY\_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. – Will G. > **[hotgazpacho](http://hotgazpacho.org/)** On Tue, Mar 2, 2010 at 1:07 PM, Jim D. \<[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)\> wrote: I believe JRuby is doing the 1st one, which makes sense in my opinion. If possible we should prefer platform == “ironruby”, (or .net, do we need to differentiate .net and mono?), but accept others. JD From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Shri B. Sent: Tuesday, March 02, 2010 10:02 AM To: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: [Ironruby-core] IronRuby version of existing gems This brings a question to mind - what should the general approach be for porting existing gems to IronRuby? There could be two possible approaches: 1. ``` Create a gem with the same name (“win32console” in this case), ``` and specify platform==”ironruby”. That way, dependent gems do not need to be updated, and users have to remember just one name. IronRuby will use the version with platform==”ironruby”, and MRI will use the one with platform==”mswin32”. So there should not be any clashes even if you use MRI and IronRuby on the same machine. 1. ``` Create a new gem like iron-term-ansicolor. ``` Any pro or cons to the two? What should the recommendation be in general? From: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Tuesday, March 02, 2010 7:47 AM To: ironruby-core Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released I released iron-term-ansicolor 0.0.3 last night after testing the gem install locally first. Please let me know if you still have trouble installing it from [Rubygems.org](http://Rubygems.org). Also, I’ve submitted a patch to RSpec to use iron-term-ansicolor if it can, the same way it tries to use win32console under MRI. – Will G. > **[hotgazpacho](http://hotgazpacho.org/)** * * * Ironruby-core mailing list [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 5, 2010, 4:36pm UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/19 "2010-03-05T16:36:06Z")
Cool beans! I noticed in the latest push that a change was made to Ruby Gems itself: [http://github.com/ironruby/ironruby/commit/82cb04621b505dea5a010c70827addc2de6227ba#diff-0](http://github.com/ironruby/ironruby/commit/82cb04621b505dea5a010c70827addc2de6227ba#diff-0) Someone should contribute that change to the Ruby Gems project as well. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) ---
**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\ **Post date:** [March 5, 2010, 1:46am UTC](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249/20 "2010-03-05T01:46:23Z")
With my last checkin, RbConfig::CONFIG[“arch”] will be “universal-.net2.0” for IronRuby. I created a gemspec as shown below. Doing “gem build” on it will create a gem with filename of Shri-1.2.3-universal-unknown.gem. Instead use “rbx –S gem build” and you will get a file called Shri-1.2.3-universal-.net.gem. spec = Gem::Specification.new do |s| s.name = ‘Shri’ s.version = ‘1.2.3’ s.summary = “Shri summary” s.platform = “universal-.net” s.description = %{Shri description} s.files = [] s.author = “Shri” s.email = “shri@email” s.homepage = “[http://shri.org](http://shri.org)” end I have updated with [http://ironruby.net/Documentation/Real\_Ruby\_Applications/RubyGems](http://ironruby.net/Documentation/Real_Ruby_Applications/RubyGems) with this info: IronRuby-specific gems Gems could specifically target IronRuby. They may contain Ruby code which uses .NET APIs, or they may even include compiled .NET assemblies. In such cases, the Gem specification should set platform [http://rubygems.org/read/chapter/20#platform](http://rubygems.org/read/chapter/20#platform) to “universal-.net” (or “universal-.net4.0” to run only on .NET 4), and build the gem using IronRuby (“rbx -S gem build”). Note that if you build the gem with MRI using “gem build”, MRI will not be able to recognize the platform string, and will create a gem file named something like foo-universal-unknown.gem (instead of the expected foo-universal-.net.gem"). To avoid this, build the gem using IronRuby as mentioned above. Talking with Tomas, we will leave RUBY\_PLATFORM set to “x86-mswin32” (on Windows) since many apps check for “mswin32” in RUBY\_PLATFORM to check if they are running on Windows. We considered appending “.net” and setting RUBY\_PLATFORM to “.net-mswin32” or “x86-mswin32/.net” to indicate that it was not MRI, but decided against it as you can always check RUBY\_ENGINE to detect if you are running on IronRuby. From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Tuesday, March 02, 2010 11:52 AM To: removed\_email\_address@domain.invalid Subject: Re: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses the RUBY\_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) On Tue, Mar 2, 2010 at 1:07 PM, Jim D. \ wrote: I believe JRuby is doing the 1st one, which makes sense in my opinion. If possible we should prefer platform == “ironruby”, (or .net, do we need to differentiate .net and mono?), but accept others. JD From: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Shri B. Sent: Tuesday, March 02, 2010 10:02 AM To: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: [Ironruby-core] IronRuby version of existing gems This brings a question to mind - what should the general approach be for porting existing gems to IronRuby? There could be two possible approaches: 1. ``` Create a gem with the same name (“win32console” in this case), ``` and specify platform==”ironruby”. That way, dependent gems do not need to be updated, and users have to remember just one name. IronRuby will use the version with platform==”ironruby”, and MRI will use the one with platform==”mswin32”. So there should not be any clashes even if you use MRI and IronRuby on the same machine. 1. ``` Create a new gem like iron-term-ansicolor. ``` Any pro or cons to the two? What should the recommendation be in general? From: removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Will G. Sent: Tuesday, March 02, 2010 7:47 AM To: ironruby-core Subject: Re: [Ironruby-core] iron-term-ansicolor 0.0.2 Released I released iron-term-ansicolor 0.0.3 last night after testing the gem install locally first. Please let me know if you still have trouble installing it from [Rubygems.org](http://Rubygems.org). Also, I’ve submitted a patch to RSpec to use iron-term-ansicolor if it can, the same way it tries to use win32console under MRI. – Will G. [http://hotgazpacho.org/](http://hotgazpacho.org/) * * * Ironruby-core mailing list removed\_email\_address@domain.invalid[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core) [Next page](https://www.ruby-forum.com/t/iron-term-ansicolor-0-0-2-released/184249.md?page=2)