From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/82103 Path: news.gmane.org!not-for-mail From: Steinar Bang Newsgroups: gmane.emacs.gnus.general Subject: Re: gnus-sync usage Date: Sat, 28 Jul 2012 23:29:48 +0200 Organization: Probably a good idea Message-ID: <87fw8bwp4j.fsf@dod.no> References: <87ehnwt27a.fsf@free.fr> <87y5m3wts6.fsf@dod.no> <878ve3prc2.fsf@free.fr> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1343511057 29588 80.91.229.3 (28 Jul 2012 21:30:57 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 28 Jul 2012 21:30:57 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M30372@lists.math.uh.edu Sat Jul 28 23:30:57 2012 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SvEbA-0007EL-9e for ding-account@gmane.org; Sat, 28 Jul 2012 23:30:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1SvEaV-0004aP-7d; Sat, 28 Jul 2012 16:30:15 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1SvEaT-0004aG-M9 for ding@lists.math.uh.edu; Sat, 28 Jul 2012 16:30:13 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1SvEaI-0007Zn-VH for ding@lists.math.uh.edu; Sat, 28 Jul 2012 16:30:13 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1SvEaG-0001fv-TU for ding@gnus.org; Sat, 28 Jul 2012 23:30:00 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SvEaF-0006aa-JT for ding@gnus.org; Sat, 28 Jul 2012 23:29:59 +0200 Original-Received: from ip-93-129-230-46.dialup.ice.net ([46.230.129.93]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 28 Jul 2012 23:29:59 +0200 Original-Received: from sb by ip-93-129-230-46.dialup.ice.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 28 Jul 2012 23:29:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 40 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ip-93-129-230-46.dialup.ice.net Mail-Copies-To: never User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:HfO2wjaU1D4IsD+zXHwXpx6GDsI= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:82103 Archived-At: >>>>> Julien Cubizolles : > 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)