Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] exception on sending a postponed message
Date: Wed, 13 Jun 2007 20:13:41 -0400	[thread overview]
Message-ID: <1181779860-sup-5207@mona> (raw)

i resumed editing the message about per-address signatures after postponing
it, and when i sent it, i got:

[Wed Jun 13 20:10:11 -0400 2007] oh crap, an exception
[Wed Jun 13 20:10:11 -0400 2007] unlocking /home/jeff/.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: 'undefined method `to_nice_s' for nil:NilClass' (error type NoMethodError)
A backtrace follows:
./lib/sup/modes/thread-index-mode.rb:450:in `text_for_thread': undefined method `to_nice_s' for nil:NilClass (NoMethodError)
        from ./lib/sup/modes/thread-index-mode.rb:432:in `regen_text'
        from ./lib/sup/util.rb:186:in `map_with_index'
        from /usr/lib/ruby/1.8/fileutils.rb:1297:in `each_with_index'
        from ./lib/sup/util.rb:186:in `each'
        from ./lib/sup/util.rb:186:in `each_with_index'
        from ./lib/sup/util.rb:186:in `map_with_index'
        from ./lib/sup/modes/thread-index-mode.rb:432:in `regen_text'
        from ./lib/sup/modes/thread-index-mode.rb:131:in `update'
         ... 11 levels...
        from ./lib/sup/mode.rb:52:in `send'
        from ./lib/sup/mode.rb:52:in `handle_input'
        from ./lib/sup/buffer.rb:178:in `handle_input'
        from bin/sup:183

thanks,

-- 
jeff covey
http://jeffcovey.net/



                 reply	other threads:[~2007-06-14  0:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1181779860-sup-5207@mona \
    --to=jeff.covey@pobox.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