From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] A maildir root source: syncing labels with maildirs (imap folders)
Date: Tue, 26 Nov 2013 17:55:16 +0100 [thread overview]
Message-ID: <1385484573-sup-869@qwerzila> (raw)
In-Reply-To: <2AC33855-6B00-42FB-9F3B-D160D8B556D4@schmeiser.org>
Excerpts from Steven Schmeiser's message of 2013-11-26 17:42:48 +0100:
>
> On Nov 26, 2013, at 10:14, Gaute Hope <eg@gaute.vetsj.com> wrote:
>
> > Excerpts from Steven Schmeiser's message of 2013-11-26 15:43:49 +0100:
> [2013-11-26 11:34:21 -0500] maildirsub set up, type: deleted, label: deleted
> [2013-11-26 11:34:21 -0500] setting up generic folders..
> [2013-11-26 11:34:21 -0500] maildirsub set up, type: generic, label: econpapers
> [2013-11-26 11:34:21 -0500] no draft source, auto-adding...
> [2013-11-26 11:34:21 -0500] starting curses
> [2013-11-26 11:34:21 -0500] loading user colors from /Users/steve/.sup/colors.yaml
> [2013-11-26 11:34:21 -0500] initializing log buffer
> [2013-11-26 11:34:21 -0500] Welcome to Sup! Log level is set to debug.
> [2013-11-26 11:34:21 -0500] initializing inbox buffer
> [2013-11-26 11:34:21 -0500] ready for interaction!
Looks good: Only econpapers is identified as a generic label, the other
folders are mapped to one of the specials.
>
> I'm now not able to run sup-sync or open some of the threads in my inbox without crashing with the following error:
>
> /usr/local/Cellar/ruby193/1.9.3-p448/lib/ruby/gems/1.9.1/gems/sup-999/bin/sup-sync:180:in `block (2 levels) in <top (required)>': NotImplementedError (NotImplementedError)
I haven't implemented :updated in sup-sync yet (see first, or possibly
second email). To update: start Sup normally, let the Sup poll _finish_
before you try to open the problematic message. This happens now and
then, when you label a message (copy to a label dir) it gets a generic
name, upon offlinimap sync it is renamed (by offlineimap) and untill a
new poll has been run the source is out of sync. Since the poll has to
finish to fix the error it is easy to trigger it again when if you start
sup again.
> I'll try starting with a clean index.
Always a good idea :)
- gaute
next prev parent reply other threads:[~2013-11-26 16:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 15:24 Gaute Hope
2013-11-25 18:23 ` [sup-devel] " Steven Schmeiser
2013-11-25 21:08 ` Matthieu Rakotojaona
2013-11-25 21:51 ` Gaute Hope
2013-11-25 22:28 ` Gaute Hope
2013-11-26 14:43 ` [sup-devel] " Steven Schmeiser
2013-11-26 15:14 ` Gaute Hope
2013-11-26 16:42 ` Steven Schmeiser
2013-11-26 16:55 ` Gaute Hope [this message]
2013-11-27 0:48 ` Steven Schmeiser
2013-11-27 6:21 ` Gaute Hope
2013-11-27 12:42 ` Steven Schmeiser
2013-11-27 13:08 ` Gaute Hope
2013-11-27 13:24 ` Gaute Hope
2013-11-27 18:32 ` Matthieu Rakotojaona
2013-11-27 21:10 ` Gaute Hope
2013-11-29 9:22 ` Gaute Hope
2013-11-27 6:23 ` Gaute Hope
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=1385484573-sup-869@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@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