From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: gnus-sync usage
Date: Sat, 28 Jul 2012 23:29:48 +0200 [thread overview]
Message-ID: <87fw8bwp4j.fsf@dod.no> (raw)
In-Reply-To: <878ve3prc2.fsf@free.fr>
>>>>> Julien Cubizolles <j.cubizolles@free.fr>:
> All this information is stored in the .newsrc file, is it not ?
Yep.
> Does gnus-sync only keeps a copy of .newsrc somewhere ?
Yes, and no. Not in the .newsrc.eld format AFAIK. And not the entire
file, just a subset of it.
With couchdb that information is stored as JSON documents. I have no
idea what the current file based sync looks like.
The gnus-sync-read function reads the latest info from the sync server
and merges it with the current .newsrc.eld content.
The gnus-sync-save function saves the latest changes as updates to the
JSON document for the group in couchdb. I have no idea what it does on
the file version.
Those are the only two functions I use in practice.
When I start gnus, I do: `M-x gnus RET M-x gnus-sync-read RET g' and
after the g I will see the updated read counts for the groups.
When one of my gnusen have added a new nntp group and do gnus-sync-read
on another gnus, I am asked if I wish to add that group. Ditto with
topics.
When I want to save, I do: `M-x gnus-sync-save RET s'
It's a little bit fragile:
- If I forget to gnus-sync-save I may lose all read marks I have added
in this session, because the gnus-sync-read of a new session will
overwrite my .newsrc.eld status with the older status on the server.
- If I forget to do gnus-sync-read at the start of the session and then
try to do gnus-sync-save I am told that I can't gnus-sync-save until
I've done gnus-sync-read (which will overwrite my current read marks
with the older saved one)
prev parent reply other threads:[~2012-07-28 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 14:00 Julien Cubizolles
2012-07-28 19:49 ` Steinar Bang
2012-07-28 20:23 ` Julien Cubizolles
2012-07-28 21:29 ` Steinar Bang [this message]
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=87fw8bwp4j.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).