Re: overriding marks for synchronization

[Ted Zlatanov <tzz@lifelogs.com>]

On Tue, 10 Aug 2010 06:55:42 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> To override the Gnus marks, is it sufficient to change
TZ> gnus-read-init-file and modify the gnus-newsrc-alist?  I'm wondering
TZ> about the Gnus Agent, for instance.

TZ> I'm asking specifically because I want to synchronize marks
TZ> automatically across several Gnus installs.  This is Gnus-only.  My plan
TZ> is to provide a few sync backends, including plain files, imap-hash, and
TZ> others.

It looks like this is the way to override read ranges and marks:

(defun gnus-synchronization-do-backends ()

;;; example: set marks
 (gnus-info-set-marks (assoc "groupname here" gnus-newsrc-alist)
  '((tick 202) (seen (197 . 201))))

;;; example: set read ranges
 (gnus-info-set-read (assoc "groupname here" gnus-newsrc-alist)
  '((1 . 203)))

;;; necessary to sync the gnus-newsrc-hashtb IIUC
 (gnus-make-hashtable-from-newsrc-alist))

I will add that function on `gnus-read-newsrc-el-hook'.

I looked at the gnus-agent but it does so much more with headers and
active file and offline caching that synchronizing just the marks would
really stretch it.  Better to create a new gnus-synchronization.el
library IMO.  Reiner or anyone else, let me know if you have an opinion.

Ted