From 800e4ed4d1db89ad07d8332ab86f8dda37237a34 Mon Sep 17 00:00:00 2001
From: Daniel Borchmann <daniel@algebra20.de>
Date: Fri, 18 Mar 2022 17:05:54 +0100
Subject: [PATCH] Try initializing the Gnus registry earlier

Somethings restarting Gnus results in many error messages whether the
`gnus-registry` seems to be nil.  Maybe initializing the registry earlier helps?
---
 init.el | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/init.el b/init.el
index 8472987..151b2e2 100644
--- a/init.el
+++ b/init.el
@@ -1858,9 +1858,9 @@
             ;; Use Gnus’ registry; doing this too early conflicts with `gnus'
             ;; calling `gnus-shutdown', which in turn calls
             ;; `gnus-registry-clear', leaving us with an empty registry upon
-            ;; startup.  So let's call this initialization right after startup,
+            ;; startup.  So let's call this initialization right before startup,
             ;; that should be fine.
-            (add-hook 'gnus-started-hook
+            (add-hook 'gnus-before-startup-hook
                       #'gnus-registry-initialize)
 
             ;; Automatic encryption if all necessary keys are present