unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bshanks3@hotmail.com, 28542@debbugs.gnu.org
Subject: bug#28542: Temporary failure in name resolution while quitting emacs
Date: Thu, 03 Dec 2020 09:47:14 +0100	[thread overview]
Message-ID: <87o8jbxoml.fsf@gnus.org> (raw)
In-Reply-To: <837dq0gsc7.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Dec 2020 17:06:48 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> > The ELisp manual says ab out kill-emacs-hook:
>> >
>> >      Because ‘kill-emacs’ can be called in situations where user
>> >      interaction is impossible (e.g., when the terminal is
>> >      disconnected), functions on this hook should not attempt to
>> >      interact with the user.  If you want to interact with the user when
>> >      Emacs is shutting down, use ‘kill-emacs-query-functions’, described
>> >      below.
>> >
>> > So I don't think we can safely ask whether to continue.
>> 
>> I don't quite interpret it that way -- this only says that if your
>> intention is to communicate with the user, then use
>> `kill-emacs-query-functions'.
>
> But your suggestion was to ask the user whether to continue -- doesn't
> that qualify as "communicating with the user"?

It does.  But the manual talks about intent -- "if you want to interact"
-- but doesn't prohibit Emacs itself from interacting with the user.
Obviously an error doesn't happen by intent.

> Then perhaps waiting for the response for some finite time would cover
> the cases where the user cannot answer the question?

Do you mean in the noninteractive case?  I don't propose to change
anything unless interactive.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-03  8:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 17:13 bug#28542: Temporary failure in name resolution while quitting emacs Baylis Shanks
2020-11-30 10:53 ` Lars Ingebrigtsen
2020-11-30 16:21   ` Eli Zaretskii
2020-12-02  9:47     ` Lars Ingebrigtsen
2020-12-02 15:06       ` Eli Zaretskii
2020-12-03  8:47         ` Lars Ingebrigtsen [this message]
2020-12-03 15:16           ` Eli Zaretskii
2020-12-04  9:34             ` Lars Ingebrigtsen
2020-12-04  9:50               ` Robert Pluim
2020-12-04 18:41                 ` Glenn Morris
2020-12-06 12:53                   ` Lars Ingebrigtsen
2020-12-04 11:42               ` Eli Zaretskii
2020-12-06 12:50                 ` Lars Ingebrigtsen
2020-12-06 19:17                   ` Eli Zaretskii
2020-12-07 14:43                     ` Lars Ingebrigtsen
2020-12-07 16:01                       ` Eli Zaretskii
2020-12-07 16:16                         ` Lars Ingebrigtsen

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=87o8jbxoml.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=28542@debbugs.gnu.org \
    --cc=bshanks3@hotmail.com \
    --cc=eliz@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.
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).