From: martin rudalics <rudalics@gmx.at>
To: Roland Winkler <winkler@gnu.org>
Cc: 20538@debbugs.gnu.org
Subject: bug#20538: 24.4; Attempt to delete a surrogate minibuffer frame
Date: Mon, 11 May 2015 12:08:39 +0200 [thread overview]
Message-ID: <55507FA7.7020906@gmx.at> (raw)
In-Reply-To: <46510.69799.372989.21839@gargle.gargle.HOWL>
>> It probably happens because ediff (by default) display the "control
>> panel" in a frame without minibuffer and Emacs doesn't allow to make
>> such a frame the last remaining one.
>
> Not exactly.
>
> In the meanwhile, I noticed that the bug can be reproduced as
> follows:
>
> emacs -Q foo bar
>
> M-x ediff-buffers ; to compare buffers foo and bar
>
> ; select buffer foo
>
> C-x 5 2 ; display buffer foo in a 2nd window in new frame
>
> ; in the frame displaying buffers foo and bar
>
> M-x delete-frame
>
> Error: Attempt to delete a surrogate minibuffer frame
Because the "frame displaying buffers foo and bar" is the frame that has
the minibuffer for the minibuffer-less "frame displaying the Ediff
control panel". As I said above you are not allowed to delete the frame
with the minibuffer because that would make the minibuffer-less frame
the last remaining one.
> ; select the frame displaying the Ediff control panel
>
> M-x delete-frame
>
> Success!
That frame has no minibuffer. Hence it cannot possibly serve as
surrogate minibuffer frame and you can delete it without any problems.
> It seems this should be the other way round: the "surrogate
> minibuffer attribute" should be given to the frame displaying the
> Ediff control panel instead of the frame displaying buffers foo and bar.
The surrogate minibuffer frame is the one whose minibuffer substitutes
the non-existing minibuffer of the control panel frame. This is how
ediff sets things up.
martin
next prev parent reply other threads:[~2015-05-11 10:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 19:35 bug#20538: 24.4; Attempt to delete a surrogate minibuffer frame Roland Winkler
2015-05-10 2:41 ` Eli Zaretskii
2015-05-10 12:30 ` martin rudalics
2015-05-10 19:46 ` Roland Winkler
2015-05-10 20:17 ` Drew Adams
2015-05-11 3:27 ` Stefan Monnier
2015-05-11 10:08 ` martin rudalics [this message]
2015-05-11 17:03 ` Roland Winkler
2015-05-12 9:36 ` martin rudalics
2015-05-12 19:42 ` Roland Winkler
2015-05-13 7:32 ` martin rudalics
2015-05-13 15:11 ` Roland Winkler
2015-05-14 10:13 ` martin rudalics
2015-05-16 19:16 ` Roland Winkler
2015-05-19 9:42 ` martin rudalics
2015-05-19 16:12 ` Roland Winkler
2015-05-20 9:50 ` martin rudalics
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=55507FA7.7020906@gmx.at \
--to=rudalics@gmx.at \
--cc=20538@debbugs.gnu.org \
--cc=winkler@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).