From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: overriding marks for synchronization
Date: Wed, 18 Aug 2010 08:42:13 -0500 [thread overview]
Message-ID: <87pqxgdolm.fsf@lifelogs.com> (raw)
In-Reply-To: <87lj85cbms.fsf@dod.no>
On Tue, 17 Aug 2010 20:55:23 +0200 Steinar Bang <sb@dod.no> wrote:
>>>>>> Didier Verna <didier@xemacs.org>:
>> Ah, yeah that makes sense. In fact I avoid the problem by always
>> connecting to the same nntp servers through (different) tunnels. But
>> one might not be able to do that all the time.
SB> Actually the servers have to be the same (the same server names matching
SB> the same underlying NNTP servers). If not, the article numbers won't
SB> match.
SB> But what I have, and I'm guessing Ted has, is the same servers (in my
SB> case news.gmane.org, news.eclipse.org and news.opera.com) with a
SB> different subset of groups on different Gnusen.
SB> In particular, a different subset of gmane groups.
SB> And for those gmane groups that overlap, I prefer to only read the new
SB> stuff once.
Right. My setup is:
work: server A has groups P, Q, R; server B has groups X, Y, Z
home: server A has groups P, Q; server B is not available
I considered storing the marks on a per-server basis (providing storage
for marks like IMAP does internally, for example). But I think
gnus-sync.el can be used to synchronize more: the topic hierarchy and
parameters, for instance. In this it also will be more powerful than
gnus-agent.el and that's why I didn't just use that code.
Ted
next prev parent reply other threads:[~2010-08-18 13:42 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
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 [this message]
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=87pqxgdolm.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).