[sup-talk] messages wrongly labeled as drafts

[jeff covey]

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/