From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: Re: nnml suddenly not activating groups on startup
Date: Tue, 25 Aug 2020 20:59:17 -0700 [thread overview]
Message-ID: <877dtm12i2.fsf@hope.eyrie.org> (raw)
In-Reply-To: <87zh6itacs.fsf@hope.eyrie.org> (Russ Allbery's message of "Tue, 25 Aug 2020 19:22:11 -0700")
Russ Allbery <eagle@eyrie.org> writes:
> Suddenly today when I start Gnus most (but not all!) of my nnml groups
> do not activate and show in the group buffer with * for the article
> count. Pressing enter on a group to read it activates it and then
> everything is fine, including the marks. C-c M-g to activate all groups
> fixes the problem. But when I exit and restart Gnus, or use R, the
> problem recurs.
This is with Gnus v5.13 as shipped with Emacs 26.3.
To hopefully narrow this down, if after pressing R, I run:
M-: (gnus-get-unread-articles)
l
then all the groups are activated and everything is fine. So running
gnus-get-unread-articles (such as via gnus-group-get-new-news) does
activate all of the groups. I think that rules out any problems with
group activation levels (which regardless haven't changed).
gnus-setup-news should be calling gnus-get-unread-articles, however, so
I'm a bit mystified by this. I think there's either some state which is
not properly intialized when gnus-setup-news calls
gnus-get-unread-articles but that is then working properly when I call it
later, or somehow dont-connect is set and is being passed in. If that's
the case, I'm not sure why -- I'm certainly not passing it in!
--
Russ Allbery (eagle@eyrie.org) <https://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2020-08-26 4:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 2:22 Russ Allbery
2020-08-26 3:59 ` Russ Allbery [this message]
2020-08-26 7:59 ` Adam Sjøgren
2020-08-26 17:19 ` Russ Allbery
2020-08-26 18:00 ` Adam Sjøgren
2020-08-26 21:00 ` Russ Allbery
2020-08-26 22:09 ` Eric Abrahamsen
2020-08-26 22:25 ` Russ Allbery
2020-08-26 23:01 ` Eric Abrahamsen
2020-08-26 23:23 ` Russ Allbery
2020-08-27 9:43 ` Adam Sjøgren
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=877dtm12i2.fsf@hope.eyrie.org \
--to=eagle@eyrie.org \
--cc=ding@gnus.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).