Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: where is the gnus-sync documentation?
Date: Tue, 08 Nov 2011 22:53:32 +0100	[thread overview]
Message-ID: <87hb2ez3fn.fsf@dod.no> (raw)
In-Reply-To: <m2ehxiz65z.fsf@boostpro.com>

>>>>> Dave Abrahams <dave@boostpro.com>:
> on Sun Nov 06 2011, Steinar Bang <sb-AT-dod.no> wrote:

>>>>>>> Dave Abrahams <dave@boostpro.com>:

>>> I want to understand what this module is for

>> Personally, I use gnus-sync v1 to sync nntp tick marks between three
>> different gnus installations (home desktop, home netbook, and work).

> That's what I figured, roughly.

>> But the new version of gnus-sync is capable of more.

> what, specifically?

I'm not quite sure yet.  Topics for one thing.  Ted would know.

>>> and how to use it.

>> Ah... that bit is still in the process of being nailed out, I think...?

> Even some very rough tutorial/getting started guide would be lovely.

Ok, from gnus-sync.el:

 1. install CouchDB, set up a real server admin user, and create a
 database, e.g. "tzz" and save the URL,
 e.g. http://lesync.info:5984/tzz

 2. run `M-: (gnus-sync-lesync-setup "http://lesync.info:5984/tzz" "tzzadmin" "mypassword" "mysalt" t t)'

    (If you run it more than once, you have to remove the entry from
    _users yourself.  This is intentional.  This sets up a database
    admin for the "tzz" database, distinct from the server admin
    user in (1) above.)

Then add the following to your .gnus.el (adjust the URL as appropriate):
 (setq gnus-sync-backend '(lesync "http://lesync.info:5984/tzz")
       gnus-sync-newsrc-groups '("nntp" "nnrss"))

Then start using the sync database:

Initially save the current read state to the database:
    `C-u M-x gnus-sync-save RET'
(the prefix makes it save the current state of all groups)

On later sessions do `M-x gnus-sync-read RET' after starting gnus, and then
a `g' to fix the read count.

After reading some nntp stuff, you can do `M-x gnus-sync-save RET' at
any point in time (it takes hardly any time at all).




  reply	other threads:[~2011-11-08 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06 21:22 Dave Abrahams
2011-11-06 22:07 ` Steinar Bang
2011-11-08 20:54   ` Dave Abrahams
2011-11-08 21:53     ` Steinar Bang [this message]
2011-11-09  0:44     ` Ted Zlatanov

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=87hb2ez3fn.fsf@dod.no \
    --to=sb@dod.no \
    --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).