* [sup-talk] uninitialized constant problem
@ 2007-11-15 16:26 shivan
2007-11-15 17:42 ` William Morgan
0 siblings, 1 reply; 2+ messages in thread
From: shivan @ 2007-11-15 16:26 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* [sup-talk] uninitialized constant problem
2007-11-15 16:26 [sup-talk] uninitialized constant problem shivan
@ 2007-11-15 17:42 ` William Morgan
0 siblings, 0 replies; 2+ messages in thread
From: William Morgan @ 2007-11-15 17:42 UTC (permalink / raw)
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 <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-15 17:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-11-15 16:26 [sup-talk] uninitialized constant problem shivan
2007-11-15 17:42 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox