Note that there are some explanatory texts on larger screens.

plurals
  1. POwin32console installed, doesn't 'require' as expected
    text
    copied!<p>Win32Console <em>did</em> install:</p> <pre><code>Fetching: win32console-1.3.0-x86-mingw32.gem (100%) Successfully installed win32console-1.3.0-x86-mingw32 1 gem installed Installing ri documentation for win32console-1.3.0-x86-mingw32... Installing RDoc documentation for win32console-1.3.0-x86-mingw32... </code></pre> <p>but it doesn't want to work with <code>require</code>. I see this everywhere:</p> <pre><code>require 'Win32/Console/ANSI' </code></pre> <p>But everytime I try it a <code>LoadError</code> is raised.</p> <p>Is there something I'm missing here? Do I need to configure it somehow?</p> <p>P.S.:</p> <p>The error message:</p> <pre><code>LoadError: no such file to load -- Win32/Console/ANSI from path/custom_require.rb:36:in `require' from path/custom_require.rb:36:in `require' from (irb):23 from path/irb:12:in `&lt;main&gt;' </code></pre> <hr> <p><code>gem list win32console</code> gives:</p> <pre><code>*** LOCAL GEMS *** win32console (1.3.0 x86-mingw32) </code></pre> <hr> <p><code>gem environment</code> gives:</p> <pre><code>RubyGems Environment: - RUBYGEMS VERSION: 1.7.2 - RUBY VERSION: 1.9.2 (2011-07-09 patchlevel 290) [i386-mingw32] - INSTALLATION DIRECTORY: rubypath/lib/ruby/gems/1.9.1 - RUBY EXECUTABLE: rubypath/bin/ruby.exe - EXECUTABLE DIRECTORY: rubypath/bin - RUBYGEMS PLATFORMS: - ruby - x86-mingw32 - GEM PATHS: - rubypath/lib/ruby/gems/1.9.1 - userpath/.gem/ruby/1.9.1 - GEM CONFIGURATION: - :update_sources =&gt; true - :verbose =&gt; true - :benchmark =&gt; false - :backtrace =&gt; false - :bulk_threshold =&gt; 1000 - REMOTE SOURCES: - http://rubygems.org/ </code></pre> <p>(paths truncated because they are long)</p> <hr> <p>Finally: <code>ruby -v</code>:</p> <pre><code>ruby 1.9.2p290 (2011-07-09) [i386-mingw32] </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload