From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup crashing upon save changes ($)
Date: Tue, 03 Nov 2009 05:43:25 -0800 [thread overview]
Message-ID: <1257255713-sup-617@masanjin.net> (raw)
In-Reply-To: <1256178926-sup-1780@Richard-Sandilandss-MacBook-Pro.local>
Reformatted excerpts from Richard Sandilands's message of 2009-10-21:
> I'm tracking next and when I hit $, sup crashes and logs this:
>
> Any clues on how to get things ironed out would be appreciated.
>
> Exception log:
>
> --- Errno::ENOENT from thread: load messages for thread-view-mode
> No such file or directory - /Users/richard/.sup/drafts/18
It looks like Sup's expecting a draft message that disappeared from disk
somehow. You should be able to fix this by reindexing the drafts folder:
sup-sync --all -v sup://drafts
But you may want to find out why that file disappeared.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-03 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 2:36 Richard Sandilands
2009-11-03 13:43 ` William Morgan [this message]
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=1257255713-sup-617@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.org \
/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