From: Tassilo Horn <tsdh@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: The Gnus registry could not be loaded from ~/.gnus.registry.eioio, creating a new one
Date: Tue, 23 Apr 2013 19:19:51 +0200 [thread overview]
Message-ID: <87bo95p3k8.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <871ua12ztp.fsf@free.fr>
Julien Cubizolles <j.cubizolles@free.fr> writes:
> I very often see this error message when starting Gnus. It's very
> inconvenient since the registry is then recreated from scratch and
> I've no idea what is going wrong, the error message isn't very
> helpful.
>
> Here is my setup:
> * I run Gnus on two machines mostly unplugged, with gnus-agent-fetch run
> from a cron job
> * I synchronize the ~/Mail and ~/News directories, the ~/.gnus.el
> ~/.gnus.registry.eioio and ~/.gnus.registry.eld on these two machines with unison
>
> Is there any reason why it shouldn't work ?
Are you using two different emacs versions on the two machines? If so,
it might be that the eieio format used by the registry changed between
those versions.
Bye,
Tassilo
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2013-04-23 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 12:31 Julien Cubizolles
2013-04-23 17:19 ` Tassilo Horn [this message]
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=87bo95p3k8.fsf@thinkpad.tsdh.de \
--to=tsdh@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).