From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 45330@debbugs.gnu.org
Subject: bug#45330: 28.0.50; debbugs-gnu: Can't select reports before having started Gnus
Date: Wed, 23 Dec 2020 10:08:47 -0800 [thread overview]
Message-ID: <87tuscz974.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sg7xrt82.fsf@web.de> (Michael Heerdegen's message of "Wed, 23 Dec 2020 06:23:25 +0100")
On 12/23/20 06:23 AM, Michael Heerdegen wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Oh hang on, it looks like that took me several tries to get right,
>> in a81223aeaa, 87b7c06958, a34216351f, and then finally ae76ce57cf,
>
> Wow...
It was embarrassing.
>> in which it looks like I was confident that checking
>> `gnus-registry-enabled' was sufficient to ensure that the registry was
>> actually an object. Give me a second to figure out why that's not
>> true.
>
> Ok, please keep me informed :-)
So it's pretty clear: `gnus-registry-initialize' in effect looks like
this:
(defun gnus-registry-initialize ()
(gnus-registry-install-hooks) -> (setq gnus-registry-enabled t)
(if (gnus-alive-p)
(gnus-registry-load)
(add-hook 'gnus-read-newsrc-el-hook #'gnus-registry-load)))
So in your case `gnus-registry-enabled' is set to t, but then
`gnus-registry-load' is never called (because Gnus is neither alive, nor
loaded later).
I suppose it's still reasonable to set `gnus-registry-enabled' in this
way -- the registry is, in fact, "enabled", it simply hasn't gotten
loaded (the naming problem again!). Perhaps the formatting functions
should go back to the earlier, more explicit check of `eieio-object-p'.
Bleagh.
Eric
next prev parent reply other threads:[~2020-12-23 18:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 4:53 bug#45330: 28.0.50; debbugs-gnu: Can't select reports before having started Gnus Michael Heerdegen
2020-12-21 4:56 ` Lars Ingebrigtsen
2020-12-21 7:10 ` Michael Heerdegen
2020-12-21 16:12 ` Eric Abrahamsen
2020-12-22 16:43 ` Eric Abrahamsen
2020-12-23 5:23 ` Michael Heerdegen
2020-12-23 18:08 ` Eric Abrahamsen [this message]
2021-12-04 23:18 ` Lars Ingebrigtsen
2021-12-05 0:23 ` Michael Heerdegen
2021-12-05 19:48 ` Lars Ingebrigtsen
2021-12-05 22:18 ` Eric Abrahamsen
2021-12-06 1:14 ` Michael Heerdegen
2021-12-06 1:29 ` Eric Abrahamsen
2021-12-06 5:46 ` Lars Ingebrigtsen
2021-12-06 18:06 ` Eric Abrahamsen
2021-12-06 21:29 ` Michael Heerdegen
2021-12-06 21:45 ` Eric Abrahamsen
2021-12-06 23:01 ` Michael Heerdegen
2021-12-12 2:46 ` Michael Heerdegen
2021-12-23 22:42 ` Eric Abrahamsen
2021-12-31 18:55 ` Michael Heerdegen
2021-12-31 20:43 ` Eric Abrahamsen
2022-01-12 23:06 ` Eric Abrahamsen
2022-01-12 23:07 ` Eric Abrahamsen
2022-01-13 12:43 ` Michael Heerdegen
2022-01-13 19:42 ` Eric Abrahamsen
2022-01-13 21:54 ` Michael Heerdegen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuscz974.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=45330@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).