Excerpts from Steven Schmeiser's message of 2013-11-26 17:42:48 +0100: > > On Nov 26, 2013, at 10:14, Gaute Hope <e...@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 _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
