# Yanked 'ansicode' gem; use 'ansi' instead

**URL:** <https://www.ruby-forum.com/t/yanked-ansicode-gem-use-ansi-instead/187202>\
**Category:** Ruby\
**Created:** [April 19, 2010, 6:52pm UTC](https://www.ruby-forum.com/t/yanked-ansicode-gem-use-ansi-instead/187202 "2010-04-19T18:52:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tcsnide](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/eb8c5e/32.png) [@tcsnide](https://www.ruby-forum.com/u/tcsnide)\
**Post date:** [April 19, 2010, 6:52pm UTC](https://www.ruby-forum.com/t/yanked-ansicode-gem-use-ansi-instead/187202/1 "2010-04-19T18:52:29Z")

</div>

This is just a simple FYI, since there is no way that I know of to  
post a notice to the gem’s [rubygems.org](http://rubygems.org) page.

I finally yanked the ‘ansicode’ gem. If you were using this gem,  
please switch to the ‘ansi’ gem, its designated successor. The  
difference in usage is very simple.

ANSI::Code

instead of

ANSICode

That’s it.