From: Peter Ludemann <peter.ludemann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55560@debbugs.gnu.org
Subject: bug#55560: 29.0.50; kill-emacs on daemon doesn't remove ~/.emacs.d/.emacs.desktop.lock
Date: Sat, 21 May 2022 13:43:42 -0700 [thread overview]
Message-ID: <CAHjfyZ3MdfvysMz-dxKTdswUC2Wyj7FAb_Pvu4jwfWzMHWVVmw@mail.gmail.com> (raw)
In-Reply-To: <837d6e8y27.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
The various wikis are somewhat out of date. For example, this shows how to
create custom functions that do what save-buffers-kill-emacs does:
https://www.emacswiki.org/emacs/EmacsAsDaemon
Also, the documentation for kill-buffers and save-buffers-kill-emacs makes
no mention of the lock file.
Anyway, when I do "emacs --daemon -Q", "emacsclient -e
'save-buffers-kill-emacs'" worked fine; but when I run the daemon without
the "-Q", the "emacs -e 'save-buffers-kill-emacs'" command just sits there
with no output. The problem seems to be that I have this in my .emacs:
(setq kill-emacs-query-functions
(cons (lambda () (yes-or-no-p "Really kill Emacs? "))
kill-emacs-query-functions))
which sets kill-emacs-query-functions to:
((lambda nil
(yes-or-no-p "Really kill Emacs? "))
desktop-kill)
[I don't know where the "desktop-kill" comes from]
I often accidentally do ^X-^C when I run emacs in non-daemon mode, so I'd
like to keep this hook, or something similar. Is there a better way of
getting an "are you sure" message that works with both daemon and
non-daemon?
[-- Attachment #2: Type: text/html, Size: 2426 bytes --]
next prev parent reply other threads:[~2022-05-21 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 19:16 bug#55560: 29.0.50; kill-emacs on daemon doesn't remove ~/.emacs.d/.emacs.desktop.lock Peter Ludemann
2022-05-21 19:50 ` Eli Zaretskii
2022-05-21 20:43 ` Peter Ludemann [this message]
2022-05-22 5:22 ` 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=CAHjfyZ3MdfvysMz-dxKTdswUC2Wyj7FAb_Pvu4jwfWzMHWVVmw@mail.gmail.com \
--to=peter.ludemann@gmail.com \
--cc=55560@debbugs.gnu.org \
--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).