Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: overriding marks for synchronization
Date: Thu, 12 Aug 2010 14:56:25 -0500	[thread overview]
Message-ID: <87y6cbehau.fsf@lifelogs.com> (raw)
In-Reply-To: <87d3tpmft7.fsf@lifelogs.com>

On Wed, 11 Aug 2010 08:36:52 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Wed, 11 Aug 2010 10:51:33 +0200 Steinar Bang <sb@dod.no> wrote: 
>>>>>>> Ted Zlatanov <tzz@lifelogs.com>:
>>> I'm asking specifically because I want to synchronize marks
>>> automatically across several Gnus installs.  This is Gnus-only.  My
>>> plan is to provide a few sync backends, including plain files,
>>> imap-hash, and others.

SB> That is a feature I want! :-)

SB> Primarily for the nntp backend.  The imap backend synchronizes itself,
SB> once I've visited  the groups.

TZ> Yeah, any backend that doesn't keep marks on a server.  So nntp and
TZ> nnrss would be the main candidates, though I dearly hope nnrss fades
TZ> into oblivion now that gwene is available.

See gnus-sync.el, just comitted (I worked on it last night and tested it
today).  It's harmless unless you set the gnus-sync-backend to a
filename, in which case it will start synchronizing to that file.  It's
most useful, of course, when the file is remote over FTP or SSH or IMAP
(did you know Tramp supports reading and writing files as messages in an
IMAP mailbox?)

It uses cl.el liberally.  I like the loop syntax, dolist, and setf.

Ted




  reply	other threads:[~2010-08-12 19:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 11:55 Ted Zlatanov
2010-08-11  3:18 ` Ted Zlatanov
2010-08-11  8:51 ` Steinar Bang
2010-08-11 13:36   ` Ted Zlatanov
2010-08-12 19:56     ` Ted Zlatanov [this message]
2010-08-13 12:26       ` Steinar Bang
2010-08-13 12:44         ` Steinar Bang
2010-08-13 12:52         ` Ted Zlatanov
2010-08-13 13:29           ` Ted Zlatanov
2010-08-13 14:12             ` Steinar Bang
2010-08-13 14:29               ` Ted Zlatanov
2010-08-13 18:41                 ` Steinar Bang
2010-08-13 19:39                 ` Steinar Bang
2010-08-13 19:58                   ` Ted Zlatanov
2010-08-14 13:38                     ` Steinar Bang
2010-08-14 14:55                       ` Ted Zlatanov
2010-08-15 11:18                         ` Steinar Bang
2010-08-18 13:44                           ` Ted Zlatanov
2010-08-30 15:59                             ` Steinar Bang
2010-08-30 16:06                               ` Steinar Bang
2010-08-31 18:52                                 ` Ted Zlatanov
2010-08-31 18:50                               ` Ted Zlatanov
2010-08-31 17:27                             ` Steinar Bang
2010-09-02  7:53                               ` Steinar Bang
2010-08-13 18:48           ` Steinar Bang
2010-08-13 19:47             ` Ted Zlatanov
2010-08-15 16:35 ` Didier Verna
2010-08-15 16:39   ` Steinar Bang
2010-08-15 17:20     ` Didier Verna
2010-08-17 18:55       ` Steinar Bang
2010-08-18 13:42         ` Ted Zlatanov
2010-08-22  8:21           ` Steinar Bang

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=87y6cbehau.fsf@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).