Re: gnus-cloud.el

[Eric Abrahamsen <eric@ericabrahamsen.net>]

David Edmondson <dme@dme.org> writes:

> After some time away, I'm playing with Gnus again. In this instance,
> gnus-cloud isn't working for me.
>
> Specifically, I can add a gnus-cloud storage server (on nnimap) and
> register another server (nntp) with it. ~u causes messages to be added
> to Emacs-Cloud and they appear to have the right kind of content.
>
> ~d on another machine never does anything useful (e.g. mark some
> articles as read) because this test:
>
>               (if (and newer (not force-older))
>                 (gnus-message 3 "Skipping outdated cloud info for group %s, the info is from %s (now is %s)" group date now)
>
> always returns true.
>
> Looking at how `newer' is calculated, it compares the group timestamp
> from the gnus-cloud message with the current time. It's not clear to me
> how that test is ever going to return `nil', unless I have a version of
> emacs running somewhere in the future that updates gnus-cloud.

It's true that doesn't make a lot of sense. Presumably we should be
checking against some value from `gnus-cloud-file-timestamps' instead.

And now that there's a iso8601 library, it would also be nice to use
that along with `time-less-p', instead of these string comparisons.

> Forcing `newer' to `nil' for debugging does indeed cause the local gnus
> to pay attention to changes from the cloud.
>
> Is this all expected to be working at the moment? The logic has not
> changed for quite some time (I have the patch that Paul Eggert made a
> couple of weeks ago - it doesn't seem directly relevant).

I once installed gnus-cloud, but I don't think I ever tried to use it.
I've never really looked into how it's supposed to work.

Eric