Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Mail source unreachable - continue yes/no?
Date: Tue, 12 Oct 2021 11:18:20 -0700	[thread overview]
Message-ID: <87wnmixg2b.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8735p6azz2.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> `nnmail-get-new-mail' is called from within `gnus-request-scan', and
>> there's no error ignoring around `gnus-request-scan' in
>> `gnus-get-unread-articles' -- is there? I can't see anything. I would
>> propose removing error handling from `nnmail-get-new-mail-1': if the
>> fetching of mail sources well and truly fails (and the user hits "no" to
>> give up on the process), it should just signal an error up the line.
>
> Yes, I think so...  but isn't there error handling in gnus-request-scan?
> I really thought there was...

You mean in `gnus-get-unread-articles', around `gnus-request-scan'? No,
there doesn't seem to be.

In other places where `gnus-request-scan' is called, the code is mostly
working with a single group, in which case you could argue that errors
should just bubble up to the user.

>> I think nntp servers are louder than the others. When I hit "g" and the
>> nntp connection times out, I get a "server closed connection" message,
>> and the whole update process halts.
>
> That sounds like a bug.  :-)  If I push, for instance
>
> 	(nntp "localhost")
>
> to gnus-secondary-select-methods and hit g, I get an error message and
> then the server is marked as "denied", but Gnus carries on its merry
> way.  (Same if something times out or I hit `C-g' while it's connecting.)

I've got my nntp server set in `gnus-select-method', maybe that's why?
This has annoyed me off and on for years but I've never taken the time
to look into it. My other servers are all localhost nnimap and I never
see errors there. I just set debug-on-message appropriately, and will
figure out exactly where things are going off.



  reply	other threads:[~2021-10-12 18:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  6:07 Lars-Johan Liman
2021-10-12 12:39 ` Lars Ingebrigtsen
2021-10-12 16:50   ` Eric Abrahamsen
2021-10-12 16:57     ` Lars Ingebrigtsen
2021-10-12 17:49       ` Eric Abrahamsen
2021-10-12 17:56         ` Lars Ingebrigtsen
2021-10-12 18:18           ` Eric Abrahamsen [this message]
2021-10-12 18:25             ` Lars Ingebrigtsen
2021-10-12 19:50               ` Eric Abrahamsen
2021-10-13 11:33                 ` Lars Ingebrigtsen
2021-10-14  5:03                   ` Eric Abrahamsen
2021-10-14 11:22                     ` Lars Ingebrigtsen
2021-10-14 18:31                       ` Eric Abrahamsen
2021-10-15 10:42                         ` Lars Ingebrigtsen
2021-10-15 17:43                           ` Eric Abrahamsen
2021-10-12 16:57   ` Lars-Johan Liman
2021-10-14 17:39     ` Eric Abrahamsen
2021-10-15 10:48       ` Lars Ingebrigtsen
2021-10-15 17:52         ` Eric Abrahamsen
2021-10-18  6:42           ` Lars Ingebrigtsen
2021-10-18 15:03             ` Eric Abrahamsen
2021-10-19 13:42               ` Lars Ingebrigtsen
2021-10-19 15:15                 ` Eric Abrahamsen
2021-10-21 23:36               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wnmixg2b.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=info-gnus-english@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.
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).