From mboxrd@z Thu Jan  1 00:00:00 1970
From: kingshivan@gmail.com (shivan)
Date: Thu, 15 Nov 2007 17:26:36 +0100
Subject: [sup-talk] uninitialized constant problem
Message-ID: <1e5fdab70711150826v2e916586t19c7bc150af92c34@mail.gmail.com>

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
[Thu Nov 15 17:25:16 +0100 2007] locking /home/shivan/.sup/lock...
[Thu Nov 15 17:25:16 +0100 2007] stopped cursing
[Thu Nov 15 17:25:16 +0100 2007] oh crap, an exception
[Thu Nov 15 17:25:16 +0100 2007] unlocking /home/shivan/.sup/lock...
----------------------------------------------------------------
I'm very sorry, but it seems that an error occurred in Sup.
Please accept my sincere apologies. If you don't mind, please
send the backtrace below and a brief report of the circumstances
to sup-talk at rubyforge dot orgs so that I might address this
problem. Thank you!

Sincerely,
William
----------------------------------------------------------------

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.
my only source is an mbox file of my gmail account (sup-sync
--all-sources died a few times before indexing it completely)

any idea ?

-- 
shivan