Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: nnml suddenly not activating groups on startup
Date: Tue, 25 Aug 2020 19:22:11 -0700	[thread overview]
Message-ID: <87zh6itacs.fsf@hope.eyrie.org> (raw)

I'm having a very strange issue and am not sure where to look in debugging
it.

I have Gnus configured with nntp as the primary select method and nnml as
the secondary select method, and have a ton of nnml groups.  Due to an
unrelated problem, I've recently had to C-g during a "g" command to check
for new mail and news a few times.  Other than that, no versions or other
configuration have changed.

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.

Nothing has changed in my startup files and I can't find anything in
newsrc.eld that would be relevant.  Clearly Gnus is storing some state
somewhere, but I have no idea where and can't find it.

Where should I be looking?

-- 
Russ Allbery (eagle@eyrie.org)             <https://www.eyrie.org/~eagle/>


             reply	other threads:[~2020-08-26  2:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26  2:22 Russ Allbery [this message]
2020-08-26  3:59 ` Russ Allbery
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=87zh6itacs.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).