[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-st
From: |
Jim Porter |
Subject: |
bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files |
Date: |
Tue, 23 Nov 2021 15:42:59 -0800 |
Eli, Lars: I'm not sure what either of you would like to do about this
bug, but it seems that most of the conflict is due to a miscommunication
between me and Gregory (that's my impression, anyway). I hope my
previous messages have explained my thoughts on the matter fairly
thoroughly (if not, just let me know). However, I'm not sure there's
much more I can add to the discussion beyond this message.
On 11/23/2021 2:49 PM, Gregory Heytings wrote:
As I said earlier, the problem you described in this bug report was not
a bug, at least in the sense that it was not something that was not
explicitly intended by the one who wrote the code (and documented). And
the behavior you wanted is handled by the patch I sent, without removing
any of the other existing behaviors. But now you apparently want
something else again.
I've only wanted one behavior since I started this discussion on Oct
19[1]. However, rather than making sure we understand each other's
descriptions (or consulting the patches I've posted throughout the
discussion) and have properly identified the corner cases to handle,
you've instead implemented the behavior "for" me, even though I said
from the beginning that I was looking to write the patch myself. I never
posted a rigorous specification of the behavior I wanted for that
reason: I was soliciting feedback to develop a patch that meets my needs
(along with the needs of anyone who spoke up at the time, if possible).
The fact that you opted to help by authoring your own patches is
appreciated, but it ultimately doesn't help me because we seem to be
talking at cross purposes and your impressions of what I want aren't
what I actually want. Moreover, if our interpretations *don't* match up
and I bring up an issue with a proposed patch, that doesn't mean that I
want an additional option or that I've changed my mind; it just means
that we haven't reached an understanding yet.
I certainly don't expect you to do any additional work here. I'm
perfectly happy to provide patches implementing the behavior I have in
mind, and to adjust them as needed if you or anyone else has feedback on
them. While I could probably construct a rigorous specification for the
behavior I want so that someone else (e.g. you) could implement it, that
would probably end up just being a set of test cases extracted from the
patch I already have.
As an aside, I mentioned this previously, but I think it would be
valuable to write some automated test cases to verify that things work
as expected. However, I didn't see a way to test creating/destroying
Emacs servers/clients via ERT. I'm certainly open to doing so if someone
points me in the right direction though.
I don't think that a user who opts in to stopping the Emacs daemon
automatically is *also* opting in to changing the behavior of whether
Emacs will prompt about saving files when killing a (non-last) client.
Since there are other clients, the daemon won't be killed, and so the
behavior should be identical to what happens without
`server-stop-automatically'. As a user, I would find it very strange
that enabling `server-stop-automatically' would change Emacs' behavior
in ways *other than* stopping the server in certain cases.
Yet this is what you're asking. If you want Emacs to prompt you whether
the files should be saved and the process killed when you delete the
last frame, you want to change the way Emacs prompts about saving files
and killing processes, because this (namely prompting the user when the
last frame is deleted) isn't happening without server-stop-automatically.
That's not relevant to the case I'm discussing above. I specifically
said I'm talking about the behavior when killing the *non-last* client.
In that case, the server won't be stopped, no matter how
`server-stop-automatically' is configured.
[1] https://lists.gnu.org/archive/html/emacs-devel/2021-10/msg01465.html
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Jim Porter, 2021/11/19
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Eli Zaretskii, 2021/11/20
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Gregory Heytings, 2021/11/23
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Jim Porter, 2021/11/23
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Gregory Heytings, 2021/11/23
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Jim Porter, 2021/11/23
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Gregory Heytings, 2021/11/23
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files,
Jim Porter <=
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Gregory Heytings, 2021/11/23
- bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Jim Porter, 2021/11/23
bug#51993: 29.0.50; [PATCH] Killing emacsclient terminal with `server-stop-automatically' doesn't prompt to save files, Jim Porter, 2021/11/29