From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Keeping multiple imap-and-nntp-based gnusae in sync
Date: Tue, 15 Apr 2003 06:30:51 -0400 [thread overview]
Message-ID: <d6jooxwk.fsf@asfast.com> (raw)
In-Reply-To: <iluvfxgcifs.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 15 Apr 2003 09:45:43 +0200")
Simon Josefsson <jas@extundo.com> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> [ ... ]
>>
>> Has anyone invented a procedure for sync-ing marks and article statuses
>> across multiple versions of gnus?
>
> For IMAP, the server should keep all state, for NNTP you have to sync
> .newsrc.eld or similar. If the IMAP server doesn't support
> client-specific flags, Gnus specific flags (e.g., expired and dormant)
> won't be synced either. Read flags should definitely be synced
> though. Does it help to press M-g before entering a group? Did you
> mean they weren't synced in the group buffer (unread article count),
> or in the summary buffer? The former is a known bug, but the latter
> should work.
Yes, I was confused by the unread article count in the group buffer.
The actual read and unread articles indeed show up properly in the
summary buffer.
With regard to the gnus-specific flags (expired, dormant, etc.) and the
nntp state: is it sufficient that I sync `.newsrc.eld', or do I have to
sync other items, as well? ... what about `.newsrc' (without the `.eld'
suffix)?
Thanks for your help.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~2003-04-15 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 23:41 Lloyd Zusman
2003-04-15 7:45 ` Simon Josefsson
2003-04-15 10:30 ` Lloyd Zusman [this message]
2003-04-15 16:10 ` Simon Josefsson
2003-04-15 16:08 ` David S Goldberg
2003-04-17 18:43 ` Kai Großjohann
2003-04-17 18:55 ` Lloyd Zusman
2003-04-17 19:07 ` Ted Zlatanov
2003-04-22 6:56 ` Niklas Morberg
2003-04-22 12:57 ` Kai Großjohann
2003-04-22 13:24 ` Ted Zlatanov
2003-04-22 13:19 ` Ted Zlatanov
2003-04-22 13:31 ` Sean Neakums
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=d6jooxwk.fsf@asfast.com \
--to=ljz@asfast.com \
/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).