Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] messages wrongly labeled as drafts
Date: Thu, 16 Aug 2007 21:20:33 -0400	[thread overview]
Message-ID: <1187313405-sup-8302@mona> (raw)

i postponed a message, then came back to it, finished it, and sent it.  the
thread still appears with a "draft" label, which i can't remove.  there are
currently no draft messages waiting to be finished, but if i hit "R", i get
this exception:


[Thu Aug 16 21:16:01 -0400 2007] stopped cursing
[Thu Aug 16 21:16:01 -0400 2007] oh crap, an exception
[Thu Aug 16 21:16:01 -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: 'not a draft' (error type RuntimeError)
A backtrace follows:
./lib/sup/message.rb:156:in `draft_filename': not a draft (RuntimeError)
        from ./lib/sup/modes/resume-mode.rb:8:in `initialize'
        from bin/sup:253:in `new'
        from bin/sup:253


thanks,

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



             reply	other threads:[~2007-08-17  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17  1:20 jeff covey [this message]
2007-08-20  5:15 ` William Morgan
2007-08-20 10:04   ` jeff covey
2007-08-20 12:28     ` jeff covey
2007-08-20 17:01     ` William Morgan
2007-08-21 18:19       ` jeff covey
2007-08-23 17:40         ` William Morgan
2007-08-23 22:05           ` jeff covey

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=1187313405-sup-8302@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