From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 36765@debbugs.gnu.org
Subject: bug#36765: 27.0.50; gnus-group-split-setup should delay until Gnus has finished starting up
Date: Mon, 22 Jul 2019 11:22:53 -0700 [thread overview]
Message-ID: <87lfwq6i9u.fsf@ericabrahamsen.net> (raw)
The Gnus manual instructs users to put a call to
`gnus-group-split-setup' in their gnus.el file if they want to skip over
some tedious manual configuration.
The problem with this is that the function has:
(gnus-group-split-update)
(when auto-update
(add-hook 'nnmail-pre-get-new-mail-hook 'gnus-group-split-update))
Meaning that `gnus-group-split-update' is called immediately when this
function is run, which happens before Gnus is done starting up.
split-update calls `gnus-group-split-fancy' which ends up accessing
group parameters on all Gnus groups. Parameter access only works when
gnus-newsrc-hashtb is already initialized. When the hashtb was an
obarray, this process was a silent no-op. Now that they're hashtables,
it signals a type error.
I think a simple solution would be to change the above to:
(add-hook (if auto-update
'nnmail-pre-get-new-mail-hook
'gnus-started-hook)
'gnus-group-split-update)
Ie, if auto-update isn't passed, only run the update once, at start time.
next reply other threads:[~2019-07-22 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 18:22 Eric Abrahamsen [this message]
2019-07-23 17:21 ` bug#36765: 27.0.50; gnus-group-split-setup should delay until Gnus has finished starting up Lars Ingebrigtsen
2019-07-23 18:36 ` Eric Abrahamsen
2019-07-26 16:38 ` Eric Abrahamsen
2019-07-27 10:10 ` Lars Ingebrigtsen
2019-07-27 16:19 ` Eric Abrahamsen
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=87lfwq6i9u.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=36765@debbugs.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.
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).