From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Lars-Johan Liman <liman@liman.se>, info-gnus-english@gnu.org
Subject: Re: Mail source unreachable - continue yes/no?
Date: Mon, 18 Oct 2021 08:03:37 -0700 [thread overview]
Message-ID: <87k0iaml2u.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k0iaomva.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 18 Oct 2021 08:42:01 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> The pop-up part of it is very easy to fix, it could even be added to
>> the Gnus window configuration stuff so people can have the
>> warnings/reports visible in *Group* but not elsewhere, etc.
>
> Perhaps it could be an opt-in thing.
I'll work something up. `nnheader-report' is fine specifically for
backend-related errors, but it seems like this could fill a nice gap for
"other errors" that aren't necessarily related to a particular backend.
In the meantime, what do you think about removing the call to `error' at
the end of `nntp-report'?
next prev parent reply other threads:[~2021-10-18 15:03 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
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 [this message]
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=87k0iaml2u.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.org \
--cc=larsi@gnus.org \
--cc=liman@liman.se \
/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).