From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Missing sentinel events Date: Sun, 22 Jan 2017 19:22:19 +0100 Message-ID: <87ziijosys.fsf@gnus.org> References: <8737gbm36z.fsf@gnus.org> <87tw8rkoat.fsf@gnus.org> <83pojf3r2k.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1485109369 7565 195.159.176.226 (22 Jan 2017 18:22:49 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 22 Jan 2017 18:22:49 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cc: Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 22 19:22:44 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cVMmi-0000ob-9L for ged-emacs-devel@m.gmane.org; Sun, 22 Jan 2017 19:22:36 +0100 Original-Received: from localhost ([::1]:37318 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cVMml-00042v-MH for ged-emacs-devel@m.gmane.org; Sun, 22 Jan 2017 13:22:39 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37994) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cVMmf-00042o-Hb for emacs-devel@gnu.org; Sun, 22 Jan 2017 13:22:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cVMmb-0001HN-Iu for emacs-devel@gnu.org; Sun, 22 Jan 2017 13:22:33 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:50931) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cVMmb-0001G0-Cg; Sun, 22 Jan 2017 13:22:29 -0500 Original-Received: from 2.150.49.21.tmi.telenormobil.no ([2.150.49.21] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cVMmX-0004rJ-61; Sun, 22 Jan 2017 19:22:27 +0100 In-Reply-To: <83pojf3r2k.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 22 Jan 2017 20:08:51 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211549 Archived-At: Eli Zaretskii writes: >> From: Stefan Monnier >> Date: Sun, 22 Jan 2017 12:52:58 -0500 >> >> The "the event looks like one of the following" wording already >> implies the list is not exhaustive (and indeed, I don't think it is) > > It's supposed to be exhaustive. It was when I wrote that. If you > find a string that isn't in the list, please add it to the list. But do you think "failed with code Name lookup of laars.ingebrigtsen.no failed" message fits the "failed with code codename" template sufficiently? (The two "failed" bits is probably something that should be tweaked.) If not, do you have a suggestion as to a better sentiel code message? I like that it's so explicit: It really says what the problem was... The other messages that may appear now are: failed with code The Network Security Manager stopped the connections failed with code TLS negotiation failed And... I think that's... it? Probably. If I skim the code correctly, these are the only three newly added error conditions, and that aren't currently triggering the sentinel. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no