Memnon Anon <[email protected]> writes: > Alan Schmitt <[email protected]> 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 >> <[email protected]>' in group `nil' >> Couldn't fetch article <[email protected]> >> >> 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 _______________________________________________ info-gnus-english mailing list [email protected] https://lists.gnu.org/mailman/listinfo/info-gnus-english
