Re: [PATCH] files.el: avoid asking whether to kill Emacs multiple times

[David Kastrup <dak@gnu.org>]

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>>> If `confirm-kill-emacs' is set, but user has just been asked whether
>>> they really want to kill Emacs (for example with a ‘Modified buffers
>>> exist; exit anyway?’ prompt), do not ask them for another confirmation.
>
> I agree that skipping the second confirmation would be desirable.
>
>>> However, apply this exception only if `confirm-kill-emacs' is
>>> 'yes-or-no-p or 'y-or-n-p, otherwise this change might errenously
>>> prevent some user defined function from being run.
>
> Is it really worth the trouble?  Comparing functions is just a bad idea
> in general, so if we can avoid it, it's preferable.
>
>> Related?
>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9577
>
> Another painful one is when a file is modified outside of Emacs but you
> still want to edit the current buffer and then save it (hence
> overwriting the changes made outside of Emacs).  I think in total this
> gets you 3 confirmation prompts and at least one of them should go.

I think in connection with something like C-x v u some of the later
questions are rather hard to answer.  You just don't have a clue what
will be retained and what will be overwritten.

I have, on occasion, reverted to just doing a manual copy of the file
from the shell before daring to answer Emacs.

-- 
David Kastrup