From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] messages wrongly labeled as drafts
Date: Mon, 20 Aug 2007 10:01:11 -0700 [thread overview]
Message-ID: <1187629181-sup-1057@south> (raw)
In-Reply-To: <1187603525-sup-4036@mona>
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>
next prev parent reply other threads:[~2007-08-20 17:01 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
2007-08-20 12:28 ` jeff covey
2007-08-20 17:01 ` William Morgan [this message]
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=1187629181-sup-1057@south \
--to=wmorgan-sup@masanjin.net \
/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