Re: delete-other-frames

[Eli Zaretskii <eliz@gnu.org>]

> From: Richard Copley <rcopley@gmail.com>
> Date: Tue, 23 Aug 2016 18:56:52 +0100
> Cc: martin rudalics <rudalics@gmx.at>, Emacs Development <emacs-devel@gnu.org>
> 
> C-x b * RET ;; create and switch to buffer "*"
> M-x ediff-buffers RET RET RET ;; ediff buffers "*" and "*scratch*"
> ;; Now attempt to close the main Emacs frame using the window manager
> 
> This gives:
> 
> Debugger entered--Lisp error: (error "Attempt to delete a surrogate
> minibuffer frame")
>   delete-frame(#<frame *scratch* 00000004009c5870> t)
>   handle-delete-frame((delete-frame (#<frame *scratch* 00000004009c5870>)))
>   funcall-interactively(handle-delete-frame (delete-frame (#<frame
> *scratch* 00000004009c5870>)))
>   call-interactively(handle-delete-frame nil [(delete-frame (#<frame
> *scratch* 00000004009c5870>))])
>   command-execute(handle-delete-frame nil [(delete-frame (#<frame
> *scratch* 00000004009c5870>))] t)
>   read-event(nil t 2)
>   sit-for(2)
>   execute-extended-command(nil "toggle-debug-on-error" "t-d-o-e")
>   funcall-interactively(execute-extended-command nil
> "toggle-debug-on-error" "t-d-o-e")
>   call-interactively(execute-extended-command nil nil)
>   command-execute(execute-extended-command)
> 
> I've never been sure whether this deserves a bug report, or what
> should be the expected behaviour.

If we don't know what should be the correct behavior, how can we fix
this?

> FWIW when this happens my intention is usually to kill Emacs.

But there are more than one frame in this case, so closing one of them
can never kill Emacs anyway, even if the frame you want to delete will
be deleted.

As with any multi-window program, closing one window normally doesn't
exit the program.