From: me--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65719@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#65719: [PATCH] Pass restart argument to 'kill-emacs-query-functions'
Date: Thu, 02 Jan 2025 14:07:33 +0000 [thread overview]
Message-ID: <60592464472415a836939db15e38a8cf@elken.dev> (raw)
In-Reply-To: <86sf1xr3ep.fsf@gnu.org>
On 2024-02-12 17:35, Eli Zaretskii wrote:
> [Please use Reply All to reply, to keep everybody CC'ed.]
>
>> Date: Mon, 12 Feb 2024 17:21:04 +0000
>> From: Elken <me@elken.dev>
>>
>> The use case that raised it for me was loading perspective workspaces
>> when I restart in place (due to a
>> configuration change or other reason) but I don't want to load the
>> workspaces every time I start Emacs.
>
> And why cannot you use kill-emacs-query-functions for this purpose?
Bumping this patch again as it would be nice to have in. To answer the
question more clearly (I thought I did before, my apologies) using
kill-emacs-query-functions would technically work but also add another
prompt every time I quit or restart. It makes sense to have a clear
separation of quitting for good and restarting in place.
I also noticed this morning that `kill-emacs` and `restart-emacs` don't
handle the prefix argument for the hooks. Would you accept either
another patch for that or an amendment to this patch? The current patch
I imagine will need to be rebased anyway, so whichever is easier for
you.
Again apologies for letting this one slip so long.
Thanks all,
Ellis
next prev parent reply other threads:[~2025-01-02 14:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 19:28 bug#65719: [PATCH] Pass restart argument to 'kill-emacs-query-functions' me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-04 1:01 ` Stefan Kangas
2023-09-04 5:04 ` Elken via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-04 5:26 ` me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 11:37 ` Stefan Kangas
2023-10-15 14:32 ` Stefan Kangas
2024-02-12 14:54 ` Ellis Kenyo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-12 15:29 ` Ellis Kenyo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-12 16:53 ` Eli Zaretskii
[not found] ` <E50F6DD3-D4AA-4A51-B470-ABB496F6B113@elken.dev>
2024-02-12 17:35 ` Eli Zaretskii
2024-02-12 17:52 ` Elken via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 14:07 ` me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2025-01-04 13:09 ` Eli Zaretskii
2025-01-04 13:34 ` me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 14:14 ` Eli Zaretskii
2025-01-07 15:54 ` me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-07 16:38 ` 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=60592464472415a836939db15e38a8cf@elken.dev \
--to=bug-gnu-emacs@gnu.org \
--cc=65719@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=me@elken.dev \
--cc=stefankangas@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).