From: kingshivan@gmail.com (shivan)
Subject: [sup-talk] uninitialized constant problem
Date: Thu, 15 Nov 2007 17:26:36 +0100 [thread overview]
Message-ID: <1e5fdab70711150826v2e916586t19c7bc150af92c34@mail.gmail.com> (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
next reply other threads:[~2007-11-15 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 16:26 shivan [this message]
2007-11-15 17:42 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e5fdab70711150826v2e916586t19c7bc150af92c34@mail.gmail.com \
--to=kingshivan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox