From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 9472 invoked from network); 15 Oct 2021 17:52:50 -0000 Received: from lists.gnu.org (209.51.188.17) by inbox.vuxu.org with ESMTPUTF8; 15 Oct 2021 17:52:50 -0000 Received: from localhost ([::1]:36408 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mbRNw-0007dn-Px for ml@inbox.vuxu.org; Fri, 15 Oct 2021 13:52:48 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:36486) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbRNu-0007dd-0C for info-gnus-english@gnu.org; Fri, 15 Oct 2021 13:52:46 -0400 Received: from mail.ericabrahamsen.net ([52.70.2.18]:58996) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbRNs-0007HL-1q for info-gnus-english@gnu.org; Fri, 15 Oct 2021 13:52:45 -0400 Received: from localhost (c-71-197-232-156.hsd1.wa.comcast.net [71.197.232.156]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 3C928FA02C; Fri, 15 Oct 2021 17:52:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1634320355; bh=R284UoR5AQ3pDlHCtNWC8NGF4cF9O5ip/yCnm8koxlQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=xKbi/oqQ/CFxU9MGJ3d4KqmD+nyewrDF+DnGmu8SVG6zNXpFEkCumOrjVHIMtsk5c FQSgkzlRWgmGy7QEUYQ+rTSONz/QxBT3jbIdmrpssjdjb++Jzpsa9/XzxziE+e+jxr PFxJ1TPDvn2PfALC1aSENLFdozKNat8+Qdkt2dPA= From: Eric Abrahamsen To: Lars Ingebrigtsen Subject: Re: Mail source unreachable - continue yes/no? References: <22ee8sumb0.fsf@hiptop.liman.net> <87zgrect8z.fsf@gnus.org> <225yu241v1.fsf@hiptop.liman.net> <875ytzqzex.fsf@ericabrahamsen.net> <87k0ie4l8w.fsf@gnus.org> Date: Fri, 15 Oct 2021 10:52:33 -0700 In-Reply-To: <87k0ie4l8w.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 15 Oct 2021 12:48:15 +0200") Message-ID: <87o87qdvku.fsf@ericabrahamsen.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=52.70.2.18; envelope-from=eric@ericabrahamsen.net; helo=mail.ericabrahamsen.net X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Lars-Johan Liman , info-gnus-english@gnu.org Errors-To: info-gnus-english-bounces+ml=inbox.vuxu.org@gnu.org Sender: "info-gnus-english" Lars Ingebrigtsen writes: > Eric Abrahamsen writes: > >> Looking over the code, I'm inclined to agree with Lars-Johan here: there >> isn't really any need to halt the process, what's important is that the >> user be made aware of the failure. > > I agree. > >> Allow me to re-introduce my suggestion of using warnings! It's looking >> better and better the more I consider it. `delay-warning' is just what >> we want: it puts messages in the hopper, which aren't displayed until >> the current command is completely finished, instead of messages >> clobbering each other and getting buried. It has its own private buffer, >> keeping information separate. There are plenty of user-facing knobs, and >> facilities for hiding or silencing the warnings. > > I'm not sure I want to be popping up a buffer at the user for network > errors and the like -- it's expected that a news reader will have some > network problems, and putting up a buffer about it isn't very helpful. 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. The real advantages are 1) the warnings go into their own buffer, so they don't get lost in *Messages*, and 2) they can be displayed after the current command returns. Right now, the message about mail source failure message will never be seen by the user. We could easily emulate that behavior, it's just that warnings give it to us for free. There are other approaches, as well. I could also do a limited version of the custom error approach, only for mail sources.