From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.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 17:16:43 +0200 [thread overview]
Message-ID: <83h7p2gbs4.fsf@gnu.org> (raw)
In-Reply-To: <87o8jbxoml.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 03 Dec 2020 09:47:14 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: bshanks3@hotmail.com, 28542@debbugs.gnu.org
> Date: Thu, 03 Dec 2020 09:47:14 +0100
>
> 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.
I think the manual talks about situations where the communications are
impossible. What do we do in that case?
> > 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.
No, I was talking about the interactive case. Are you assuming that
in the interactive case it is always possible to ask a question and
get a response from the user?
next prev parent reply other threads:[~2020-12-03 15:16 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
2020-12-03 15:16 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h7p2gbs4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28542@debbugs.gnu.org \
--cc=bshanks3@hotmail.com \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.