unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Missing sentinel events
Date: Sun, 22 Jan 2017 19:22:19 +0100	[thread overview]
Message-ID: <87ziijosys.fsf@gnus.org> (raw)
In-Reply-To: <83pojf3r2k.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 22 Jan 2017 20:08:51 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> 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



  reply	other threads:[~2017-01-22 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 17:09 Missing sentinel events Lars Ingebrigtsen
2017-01-22 17:13 ` Lars Ingebrigtsen
2017-01-22 17:16 ` Lars Ingebrigtsen
2017-01-22 17:52   ` Stefan Monnier
2017-01-22 18:08     ` Eli Zaretskii
2017-01-22 18:22       ` Lars Ingebrigtsen [this message]
2017-01-22 18:42         ` Eli Zaretskii
2017-01-22 17:42 ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87ziijosys.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).