Re: gnus-cloud work

[Ted Zlatanov <tzz@lifelogs.com>]

On Fri, 01 Jul 2016 10:00:29 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote: 

EA> Oops, my misunderstanding was that I hadn't marked both a server-to-sync
EA> and a server-to-keep-syncs. Once I'd done both "i" and "I", things
EA> started going.

Yeah, sorry about that. I'll write docs when the upload+download cycle
works :)

EA> Initial bumps:

EA> gnus-cloud-synced-files doesn't match up with my files (I'd recommend
EA> the default use gnus-user-directory), and as the FIXME notes, I wasn't
EA> able to redefine it to use a different (:directory...) syntax. I set it
EA> directly to two files, and it was fine.

I'm not sure if we should even allow relative filenames. Can you think
of a use case?

EA> Weirdly, the (defvar gnus-cloud-sequence 1) didn't "work". The first
EA> time I used it, gnus-cloud-sequence was nil, and so
EA> `gnus-cloud-upload-data' threw an error in the call to `format'. I had
EA> to explicitly setq the var to 1.

EA> After that everything worked fine. I haven't yet gone to the office and
EA> tried to download the data on the other machine.
...
EA> Okay, now I've done that, and have got the sync IMAP group in both
EA> places. Once again I had to manually setq the gnus-cloud-sequence
EA> variable to make it work, and foolishly set it to 1 again, when I assume
EA> I should have set it to 2? Or...? Anyhow, now I have two messages in the
EA> sync group, both with :sequence 1. Evalling (gnus-cloud-download-data)
EA> simply returns nil.

I think I've fixed all the places where `gnus-cloud-sequence' might be
nil with a single commit to the scratch branch.

The download will grab anything with a larger sequence:

    (dolist (header (gnus-cloud-available-chunks))
      (when (> (gnus-cloud-chunk-sequence (mail-header-subject header))
               (or sequence-override gnus-cloud-sequence -1))
    ...

So if you had seq 1 in IMAP, but locally you were at 2, nothing
happened as expected.

I think `gnus-cloud-available-chunks' will grow a bit as we find edge
cases. In this case (duplicate subject) it should pick the latest
article with that subject or error out, but not accept both. But that is
a pain to do in ELisp, whereas it may be easy at the IMAP level?

Ted