Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Gnus Own-Cloudy?
Date: Wed, 11 Feb 2015 10:12:03 +0800	[thread overview]
Message-ID: <87iof9tcwc.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lhk6kn0y.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Tuesday, 10 Feb 2015 at 18:53, Eric Abrahamsen wrote:
>
> [...]
>
>> This is really helpful, thank you. Probably what I should do is simplify
>> my system a little bit, and see if I can get to the root of the problem.
>> I also like to work offline, but I use isync/dovecot for that, instead
>
> Ah, an extra variable!  I don't think it makes sense to synchronise your
> .newsrc.eld if it refers to different IMAP servers?  that is, if you
> have a local copy via isync/dovecot on each system, these are different
> servers (even if synchronised with the real IMAP server)?
>
> And, in fact, I don't see why you would want to synchronise gnus files
> if you have a local IMAP server which is already synchronising?

But I would have thought that the active values for each group are
stored on disk, so if you don't copy those over as well, Gnus will get
confused about how many messages are in each group. My understanding is
that those values are saved, not re-created, isn't that right?

> The problem with gnus, in this context, is that presentation (e.g. order
> of groups, topics etc) is intermixed with the status of individual
> groups so even though you might want to synchronise the presentation
> aspects, you cannot do this without synchronising the interaction with
> the server...  The newsrc.eld file has several functionalities combined
> unfortunately.




  parent reply	other threads:[~2015-02-11  2:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10  6:05 Eric Abrahamsen
2015-02-10  9:17 ` Eric S Fraga
2015-02-10 10:20   ` Eric Abrahamsen
2015-02-10 10:48     ` Eric S Fraga
2015-02-10 10:53       ` Eric Abrahamsen
2015-02-10 11:45         ` Eric S Fraga
2015-02-10 15:19           ` Jorge A. Alfaro-Murillo
2015-02-11  2:12           ` Eric Abrahamsen [this message]
2015-02-11 11:12             ` Eric S Fraga
2015-02-11 13:48             ` Dan Christensen
2015-02-13  5:26               ` Eric Abrahamsen
2015-02-13  5:52                 ` Eric Abrahamsen
2015-02-13 14:57                 ` Eric Abrahamsen
2015-02-14 13:48                 ` Eric Abrahamsen
2015-02-18 11:12                   ` [PATCH] " Eric Abrahamsen
2015-02-10 15:31 ` Jorge A. Alfaro-Murillo

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=87iof9tcwc.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).