From: "Roland Winkler" <winkler@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: synchronizing gnus sessions on multiple computers
Date: Fri, 10 Sep 2021 16:15:11 -0500 [thread overview]
Message-ID: <87czpgku8w.fsf@gnu.org> (raw)
In-Reply-To: <CADoYgq89o5LGPk2u-C9cg9tUUwwBX1u5sxzRwOZsHy=WF5c83A@mail.gmail.com>
On Fri, Sep 10 2021, Bob Newell wrote:
> I have rsync'd gnus for years with success. In addition to the files
> already listed I sync .newsrc.eld, but that is updated infrequently.
> Not strictly gnus entries, but related closely enough, I also sync
> .authinfo and .msmtprc (as I use msmtp) and also .bbdb.
Thanks to everyone who replied to this thread.
When you are rsyncing gnus, are you doing this while emacs is running on
the different machines? Or are you starting a fresh emacs session after
all the files got updated on a machine?
Digging through things I realized that .newsrc.eld seems to store
article marks. For example it sets gnus-newsrc-alist that holds an
assoc list of read articles. However, in a running emacs session the
same information is stored also in gnus-newsrc-hashtb. So the question
becomes: What steps are needed to fully restart gnus while emacs is
running so that internal variables such as gnus-newsrc-hashtb get
re-initialized, too.
-- I realized that testing all this does not require two different
machines. But two instances of emacs running on one computer
effectively give the same situation to play with. It seems that a
running gnus session does not warn the user that another emacs instance
has fiddled with files such as .newsrc.eld. Is this true?
next prev parent reply other threads:[~2021-09-10 21:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 23:21 Roland Winkler
2021-09-10 4:46 ` Pankaj Jangid
2021-09-10 11:06 ` Leo Butler
2021-09-10 19:45 ` Bob Newell
2021-09-10 21:15 ` Roland Winkler [this message]
2021-09-10 21:50 ` Eric Abrahamsen
2021-09-10 22:39 ` Bob Newell
2021-09-11 4:04 ` Roland Winkler
2021-10-06 4:28 ` Roland Winkler
2021-10-06 14:42 ` Eric Abrahamsen
2021-09-11 16:07 ` Greg Farough
2021-09-12 18:30 ` Bob Newell
2021-09-12 4:47 ` James Thomas
2021-10-06 4:29 ` Roland Winkler
2021-10-09 4:00 ` James Thomas
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=87czpgku8w.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=info-gnus-english@gnu.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).