From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Emacs Cloud
Date: Sat, 01 Feb 2014 16:37:16 -0500 [thread overview]
Message-ID: <87r47mqzub.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <87iosymvjg.fsf@gmx.us>
On Sat, 01 Feb 2014 21:23:47 +0100 Rasmus <rasmus@gmx.us> wrote:
R> Hi Steinar,
R> Steinar Bang <sb@dod.no> writes:
>>> I vote for being able to store all info on /one/ IMAP-server even when
>>> having several IMAP connections. My personal IMAP is very fast and my
>>> outlook.com-account is very slow.
>>
>> I use Ted's gnus-sync.el v2 with CouchDB backing, and have done so for
>> two years(?) now.
R> Thanks for pointing me to gnus-sync. How did I miss it before? I
R> have a question, though; I'd like to sync subscriptions as well as
R> read status. I have this in my init file (I don't have a separate
R> dot-gnus).
R> (setq gnus-sync-backend "/ssh:loging@server:~/gs.gpg"
R> gnus-sync-file-encrypt-to "ABCD"
R> gnus-sync-global-vars '(gnus-newsrc-last-checked-date)
R> gnus-sync-newsrc-groups '("nntp" "nnrss")
R> gnus-sync-newsrc-offsets '(2 3))
R> Stuff is synced whenever you'd expect it to be synced. But my
R> gnus-group buffer still shows different groups/subscriptions. I
R> looked for variables I could add to gs-global-vars that might serve,
R> but I didn't find any.
R> I'm probably missing something obvious.
Don't use gnus-sync. It doesn't work well (see past discussions here).
Lars' work on gnus-cloud will deprecate it.
Ted
next prev parent reply other threads:[~2014-02-01 21:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 4:55 Lars Ingebrigtsen
2014-02-01 10:11 ` Ted Zlatanov
2014-02-01 12:10 ` Rasmus
2014-02-01 16:49 ` Steinar Bang
2014-02-01 20:23 ` Rasmus
2014-02-01 21:37 ` Ted Zlatanov [this message]
2014-02-01 21:50 ` Andreas Schwab
2014-02-02 5:03 ` Ted Zlatanov
2014-02-02 8:23 ` Andreas Schwab
2014-02-04 12:55 ` Ted Zlatanov
2014-02-02 22:17 ` Steinar Bang
2014-02-01 20:48 ` Lars Ingebrigtsen
2014-02-01 21:43 ` Ted Zlatanov
2014-02-01 21:44 ` Lars Ingebrigtsen
2014-02-01 22:32 ` Lars Ingebrigtsen
2014-02-02 5:04 ` Ted Zlatanov
2014-02-02 5:14 ` Lars Ingebrigtsen
2014-02-02 5:21 ` Lars Ingebrigtsen
2014-02-02 17:17 ` Ted Zlatanov
2014-02-02 22:53 ` Lars Ingebrigtsen
2014-02-02 23:20 ` Julien Danjou
2014-02-02 23:22 ` Lars Ingebrigtsen
2014-02-02 23:39 ` Julien Danjou
2014-02-02 23:46 ` Lars Ingebrigtsen
2014-02-03 8:08 ` David Engster
2014-02-03 13:14 ` Tassilo Horn
2014-02-03 14:58 ` David Engster
2014-02-04 12:53 ` Ted Zlatanov
2014-02-04 13:25 ` David Engster
2014-02-06 0:49 ` Emacs Cloud (coverage and killed groups) Lars Ingebrigtsen
2014-02-07 2:49 ` Lars Ingebrigtsen
2014-02-07 8:56 ` Julien Danjou
2014-02-07 10:40 ` Peter Münster
2014-02-08 2:35 ` Lars Ingebrigtsen
2014-02-07 13:24 ` Ted Zlatanov
2014-02-03 14:53 ` Emacs Cloud Ted Zlatanov
2014-02-03 15:04 ` David Engster
2014-02-03 14:45 ` Ted Zlatanov
2014-02-02 17:20 ` Ted Zlatanov
2014-02-02 22:50 ` Lars Ingebrigtsen
2014-02-02 5:08 ` Ted Zlatanov
2014-02-05 7:46 ` Steinar Bang
2014-02-05 23:05 ` Lars Ingebrigtsen
2014-02-05 23:06 ` Lars Ingebrigtsen
2014-02-07 13:28 ` Ted Zlatanov
2014-02-08 4:13 ` Lars Ingebrigtsen
2014-02-10 8:43 ` Daiki Ueno
2014-02-10 13:32 ` Ted Zlatanov
2014-02-11 12:14 ` Lars Ingebrigtsen
2014-02-11 13:25 ` Daiki Ueno
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=87r47mqzub.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.com \
--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).