Re: gnus-sync.el v2

[Ted Zlatanov <tzz@lifelogs.com>]

On Sun, 02 Dec 2012 11:19:18 +0100 Andreas Schwab <schwab@linux-m68k.org> wrote: 

AS> Andreas Schwab <schwab@linux-m68k.org> writes:
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>> 
>>> Regarding gnus-sync.el, the good news is that it works great,
>> 
>> It cannot even read back what it has saved.
>> 
>> Wrong type argument: listp, 6

AS> Don't you think it is a stupid idea to change the format of the stored
AS> data without making it backward and forward compatible?

Absolutely, and if that's happened, I apologize.  But I don't recall
doing so.  I use gnus-sync daily and was not aware of this bug or design
flaw.  Can you post the backtrace and possibly the data that triggered it?

I do (really really) want to rewrite gnus-sync.el to use native IMAP
commands instead of an external CouchDB installation, and at that time
will settle on a new, more robust format for flag and general data
storage.  I was supposed to get to that last month but my work
commitment was extended by a few weeks; the rewrite is at the top of my
TODO list.

I also asked Lars for help with the IMAP side but he hasn't been
available.  If you or anyone else wants to help, I need generic
functions that, given an IMAP mailbox, a string key, and an alist, can
store the alist under the key or delete the key (so basically I want a
hashtable implemented in an IMAP mailbox).  Writing those functions will
probably be 80-90% of the time I spend on the rewrite, so any help is
appreciated.  I used to have some understanding of imap.el, but the new
nnimap.el is a super wonderful mystery to me.

Ted