From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: nnml suddenly not activating groups on startup
Date: Wed, 26 Aug 2020 15:09:26 -0700 [thread overview]
Message-ID: <87lfi1ys89.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878se1dswd.fsf@hope.eyrie.org>
Russ Allbery <eagle@eyrie.org> writes:
> Adam Sjøgren <asjo@koldfront.dk> writes:
>
>> All¹ of my mail groups have "nnml:" as the last element in
>> gnus-newsrc-alist.
>
>> I have a feeling that Gnus sometimes gets confused about servers that
>> are the same but mentioned by different definitions. Maybe going all
>> "nnml:" or all (nnml "") will unconfuse things?
>
> I tried changing everything to "nnml:" and that caused all of the groups
> to not be activated and then, in the server buffer, the nnml server was
> left closed after I started Gnus.
>
> I then changed them all to (nnml "") and that fixes the problem (but I
> suspect new groups won't have that setting).
>
> So (nnml "") seems to be doing something different than "nnml:" and is
> working correctly, and this appears to have something to do with when the
> server is opened. Maybe it's a sequencing issue during startup?
>
> For the record, my select-method configuration is:
>
> '(gnus-select-method
> '(nntp "news.eyrie.org"
> (nntp-open-connection-function network-only)
> (nntp-connection-timeout 3)))
> '(gnus-secondadry-select-methods '((nnml "")))
Just checking in to confirm that the above is a typo, and not actual
copy-and-paste from your config?
next prev parent reply other threads:[~2020-08-26 22:10 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
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 [this message]
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=87lfi1ys89.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).