From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: 56800@debbugs.gnu.org
Subject: bug#56800: Pointless "Warning: desktop file appears to be in use by PID ###."
Date: Wed, 27 Jul 2022 21:58:54 +0300 [thread overview]
Message-ID: <831qu6bcwh.fsf@gnu.org> (raw)
In-Reply-To: <CAG7Bpao5pXTqV=fuAQB0fTKYqUvxmu7YqM4udB=3Ynb2DJrOMQ@mail.gmail.com> (message from Paul Pogonyshev on Wed, 27 Jul 2022 19:52:31 +0200)
> From: Paul Pogonyshev <pogonyshev@gmail.com>
> Date: Wed, 27 Jul 2022 19:52:31 +0200
> Cc: 56800@debbugs.gnu.org
>
> Yeah, apparently `kill-emacs' is considered "low-level primitive":
>
> Functions to call with no arguments to query about killing Emacs.
> If any of these functions returns nil, killing Emacs is canceled.
> ‘save-buffers-kill-emacs’ calls these functions, but ‘kill-emacs’,
> the low level primitive, does not. See also ‘kill-emacs-hook’.
>
> Since I have rebound C-x C-c for my private use (why waste such a nice shortcut on something used once
> in a few days?), I have been using `kill-emacs'. But apparently it's not what should be used... Emacs making
> it easy to silently break things, nothing new.
>
> I suggest that `desktop-release-lock' call is still moved from something hooked on
> `kill-emacs-query-functions' to `kill-emacs-hook'. That part is supposed to be done unconditionally.
That change was made because the hook can ask questions, which doesn't
work in a daemon session. So we moved the hook.
next prev parent reply other threads:[~2022-07-27 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 16:25 bug#56800: Pointless "Warning: desktop file appears to be in use by PID ###." Paul Pogonyshev
2022-07-27 16:49 ` Eli Zaretskii
2022-07-27 16:58 ` Paul Pogonyshev
2022-07-27 17:32 ` Eli Zaretskii
2022-07-27 17:52 ` Paul Pogonyshev
2022-07-27 18:58 ` Eli Zaretskii [this message]
2022-07-27 19:22 ` Paul Pogonyshev
2022-07-28 6:17 ` 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=831qu6bcwh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56800@debbugs.gnu.org \
--cc=pogonyshev@gmail.com \
/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).