From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Memnon Anon <gegendosenfleisch@googlemail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: gnus.registry.eioio when migrating from emacs 24.1 to 24.2
Date: Thu, 27 Sep 2012 08:53:56 +0200 [thread overview]
Message-ID: <m2bogsj6rf.fsf@top-wifi.irisa.fr> (raw)
In-Reply-To: <87y5jwh9mr.fsf@mean.albasani.net> (Memnon Anon's message of "Wed, 26 Sep 2012 19:59:37 +0000 (UTC)")
Memnon Anon <gegendosenfleisch@googlemail.com> writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> Warning: The Gnus registry could not be loaded from
>> ~/.gnus.registry.eioio, creating a new one; The Gnus registry could
>> not be loaded from ~/.gnus.registry.eioio, creating a new one
> [...]
>> nnregistry: requesting article
>> <946B1446-4366-4076-ABF3-55655700E365@inria.fr>' in group `nil'
>> Couldn't fetch article <946B1446-4366-4076-ABF3-55655700E365@inria.fr>
>>
>> when I tried to find an article.
>>
>> No file "~/.gnus.registry.eioio" exists nor is created.
>
> So, I tried to set up gnus-registry; I used the same settings Alan gave
> and saw the same behavior:
>
> "The Gnus registry could not be loaded from ~/.gnus.registry.eioio,
> creating a new one"
>
> It seems the db is being created by gnus-registry-remake-db, but never
> actually saved to the file. Pressing 's' in the *Group* buffer fixed
> that (gnus-registry-save is hooked into gnus-save-newsrc-hook).
>
> Should the docs mention explicitly that a new made db must be saved
> either with M-x gnus-registry-save or 's' in the *Group* buffer?
>
> Just quitting gnus seems to execute gnus-save-newsrc without the
> optional force, the hook is not executed afaict and gnus-registry-save
> is not called: gnus-registry-cache-file is not written to disk.
>
> I hope that makes sense ...
As a followup, following Memnon's advice, I discovered that sometimes
links did not work because the .gnus.registry.eioio was out of date.
doing a save as explained above fixes it.
Alan
next prev parent reply other threads:[~2012-09-27 6:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 14:45 Alan Schmitt
2012-08-30 11:24 ` Alan Schmitt
2012-09-01 12:59 ` Alan Schmitt
2012-09-05 19:08 ` David Engster
2012-09-06 6:24 ` Alan Schmitt
2012-09-06 18:33 ` David Engster
2012-09-10 6:18 ` Alan Schmitt
2012-09-26 19:59 ` Memnon Anon
2012-09-27 6:53 ` Alan Schmitt [this message]
[not found] ` <mailman.7908.1346504390.855.info-gnus-english@gnu.org>
2012-09-05 14:11 ` Lars Ingebrigtsen
2012-09-06 6:23 ` Alan Schmitt
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=m2bogsj6rf.fsf@top-wifi.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=gegendosenfleisch@googlemail.com \
--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).