From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Keeping multiple imap-and-nntp-based gnusae in sync
Date: Tue, 15 Apr 2003 09:45:43 +0200 [thread overview]
Message-ID: <iluvfxgcifs.fsf@latte.josefsson.org> (raw)
In-Reply-To: <znmsmyub.fsf@asfast.com> (Lloyd Zusman's message of "Mon, 14 Apr 2003 19:41:16 -0400")
Lloyd Zusman <ljz@asfast.com> writes:
> I'm using a very recent version of Oort to access my imap and nntp
> servers on a central host. I have three installations of Oort on three
> separate machines, each Oort instance configured identically to point to
> the same imap and nntp servers. I do this because during the course of
> a day, I work from each of these three machines.
>
> All this works fine, except for the inconvenient fact that my marks and
> "read" statuses are local to each machine. Therefore, I find myself
> re-reading and re-marking messages when I go from machine to machine.
>
> 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.
next prev parent reply other threads:[~2003-04-15 7:45 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 [this message]
2003-04-15 10:30 ` Lloyd Zusman
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=iluvfxgcifs.fsf@latte.josefsson.org \
--to=jas@extundo.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).