From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] messages wrongly labeled as drafts
Date: Mon, 20 Aug 2007 06:04:36 -0400 [thread overview]
Message-ID: <1187603525-sup-4036@mona> (raw)
In-Reply-To: <1187586863-sup-8638@south>
Excerpts from William Morgan's message of Mon Aug 20 01:15:21 -0400 2007:
> > 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:
>
> Hm. I'm having trouble reproducing this. Are you able to reproduce it?
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.
when i restarted sup, i had three draft messages in my inbox, one for each
of my attempts (minus the one with the exception), and there are files named
"1", "2", and "3" in ~/.sup/drafts, each with a slightly different version
of the message.
[Mon Aug 20 05:51:18 -0400 2007] stopped cursing
[Mon Aug 20 05:51:18 -0400 2007] oh crap, an exception
[Mon Aug 20 05:51:18 -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:449:in `text_for_thread': undefined method `to_nice_s' for nil:NilClass (NoMethodError)
from ./lib/sup/modes/thread-index-mode.rb:431:in `regen_text'
from ./lib/sup/util.rb:233:in `map_with_index'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `each_with_index'
from ./lib/sup/util.rb:233:in `each'
from ./lib/sup/util.rb:233:in `each_with_index'
from ./lib/sup/util.rb:233:in `map_with_index'
from ./lib/sup/modes/thread-index-mode.rb:431:in `regen_text'
from ./lib/sup/modes/thread-index-mode.rb:137:in `update'
... 9 levels...
from ./lib/sup/util.rb:387:in `method_missing'
from ./lib/sup/modes/resume-mode.rb:25:in `killable?'
from ./lib/sup/buffer.rb:317:in `kill_buffer_safely'
from bin/sup:205
thanks,
--
jeff covey
http://jeffcovey.net/
next prev parent reply other threads:[~2007-08-20 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 1:20 jeff covey
2007-08-20 5:15 ` William Morgan
2007-08-20 10:04 ` jeff covey [this message]
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=1187603525-sup-4036@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