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: Tue, 10 Feb 2015 18:20:48 +0800	[thread overview]
Message-ID: <87mw4mukxr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87twyu6s7u.fsf@ucl.ac.uk>

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

> On Tuesday, 10 Feb 2015 at 14:05, Eric Abrahamsen wrote:
>> I never paid any attention to progress of Cloudy Gnus, or whatever we're
>> calling it, but then I got a desktop along with my laptop, and suddenly
>> I'm VERY INTERESTED.
>>
>> Before Cloudy is a reality, have any of you had success simply using
>> rsync between two machines?
>
> I use unison to keep 4 systems (two desktops, a laptop and a handheld
> computer, all running some version of Linux) in sync.  Unison is based
> on rsync but is a symmetric synchronisation instead of
> one-directional.  I hope that makes sense...
>
> I am not sure why you see large unread counts.  I do not.  You do have
> to be quite rigorous in the synchronisation and avoid using gnus on two
> systems simultaneously, however.

Thanks for the note! I'm quite sure I'm not using both systems at
once -- every few days I spend the day out with the laptop, and it's a
little rigmarole of updating my ~/org git repository, rsync'ing a few
other directories, and then doing my best with Gnus.

The first thing that happens is that when Gnus starts up all my nnimap
servers appear offline (or at least whatever it means when I get an
asterisk instead of unread counts next to all the group names).
Refreshing Gnus after that gives me unread counts that might be
reasonable if I *hadn't* sync'ed over the most recent marks, but for
some groups it's in the thousands, which clearly isn't right.

Is there anything you're sync'ing beyond the files/directories that I
mentioned in my first post?

Thanks!
Eric




  reply	other threads:[~2015-02-10 10:20 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 [this message]
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
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=87mw4mukxr.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).