From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Thu, 15 Nov 2007 09:42:19 -0800 Subject: [sup-talk] uninitialized constant problem In-Reply-To: <1e5fdab70711150826v2e916586t19c7bc150af92c34@mail.gmail.com> References: <1e5fdab70711150826v2e916586t19c7bc150af92c34@mail.gmail.com> Message-ID: <1195148436-sup-4453@south> Excerpts from kingshivan's message of Thu Nov 15 08:26:36 -0800 2007: > Hi, I get a error from sup when I try to start it : > > /var/lib/gems/1.8/gems/sup-0.1/lib/sup/buffer.rb:32: warning: already > initialized constant KEY_ENTER > /var/lib/gems/1.8/gems/sup-0.1/lib/sup/buffer.rb:33: warning: already > initialized constant KEY_CANCEL [snip] > The problem was: 'uninitialized constant Redwood::CanSpawnComposeMode' > (error type NameError) > A backtrace follows: > sup/bin/sup:97: uninitialized constant Redwood::CanSpawnComposeMode (NameError) > > that's with the revision 704 of the svn version. It looks like you're running the SVN version of bin/sup but it's loading code from the 0.1 gem. Run sup from SVN like this: ruby -I lib bin/sup -- William