[sup-talk] messages wrongly labeled as drafts

[William Morgan]

Excerpts from jeff.covey's message of Mon Aug 20 03:04:36 -0700 2007:
> there's definitely something odd going on with drafts.  i'm trying to
> work on another draft message now.  i started writing it and postponed
> it.  when i came back to it, added to it, and exited the editor, i hit
> "P" to postpone it again.  the next time i tried to edit it some more,
> my additions from the second editing session were gone.  i added a bit
> of text again as a trial, and when i exited the editor and postponed,
> that addition was gone as well.  i tried once again, and this time
> after exiting the editor, i hit "x" to kill the buffer.  i was asked
> "discard draft?", and when i hit "n", i got the exception below.

Bizarre. This all works for me, and has for months. Does draft saving
and resuming work for other people?

> The problem was: 'undefined method `to_nice_s' for nil:NilClass' (error type
> NoMethodError)
> A backtrace follows:
> ./lib/sup/modes/thread-index-mode.rb:449:in `text_for_thread': undefined method

Can you send me the contents of sup-exception-log.txt, which contains
the full backtrace? (The ruby stdout one elides a critical section in
this case.)

Thanks,

-- 
William <wmorgan-sup at masanjin.net>