From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Syncing gmane group read state across multiple gnusen
Date: Thu, 18 Jun 2009 14:27:35 +0200 [thread overview]
Message-ID: <kzprd1ybew.fsf@randomsample.de> (raw)
In-Reply-To: <uy6rp954k.fsf@dod.no> (Steinar Bang's message of "Thu, 18 Jun 2009 13:02:35 +0200")
Steinar Bang <sb@dod.no> writes:
>>>>>> Duncan <1i5t5.duncan@cox.net>:
>
>> Does Gnus use the standard newsrc format?
>
> Yes and no. It writes a .newsrc file for its primary NNTP server, but I
> don't know if, and if so: when, it reads it.
It reads it if gnus-read-newsrc-file is t (the default).
If will read if *after* it has read .newsrc.eld, so it should update the
read articles from .newsrc, but I never tested this. Other information
(ticked articles, killed groups, foreign/secondary methods, etc.) are
only stored in newsrc.eld, of course.
>> If it does, then what you're asking should be a breeze, because the
>> newsrc files are by definition single-server only already. Thus, it
>> would seem a natural fit for tracking status on a single shared server
>> when others aren't shared, just find the appropriate newsrc file for
>> each one and share it, leaving the others alone.
>
> Right. If I switch primary NNTP server, that isn't gmane today, _and_
> if Gnus can be persuaded to actually read the .newsrc file, then this
> should be possible.
Be aware that different servers usually have different article
numbers.
-David
next prev parent reply other threads:[~2009-06-18 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:45 Steinar Bang
2009-06-18 10:24 ` Duncan
2009-06-18 11:02 ` Steinar Bang
2009-06-18 11:42 ` Dave Goldberg
2009-06-19 11:03 ` Steinar Bang
2009-06-19 12:30 ` Vegard Vesterheim
2009-06-19 15:41 ` Steinar Bang
2009-06-18 12:27 ` David Engster [this message]
2009-06-19 11:06 ` 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=kzprd1ybew.fsf@randomsample.de \
--to=deng@randomsample.de \
--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).