From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 20538@debbugs.gnu.org
Subject: bug#20538: 24.4; Attempt to delete a surrogate minibuffer frame
Date: Sun, 10 May 2015 23:27:15 -0400 [thread overview]
Message-ID: <jwvbnhr25yu.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <46510.69799.372989.21839@gargle.gargle.HOWL> (Roland Winkler's message of "Sun, 10 May 2015 14:46:54 -0500")
> 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.
Putting "surrogate minibuffer attribute" on a frame which doesn't even
have a minibuffer wouldn't make much sense.
But I guess it would make sense to indicate that this ediff-control
frame is kind of "secondary" or "transient" or "deletable if its
minibuffer disappears". Maybe we could solve this one with a kind of
delete-window-hook similar to kill-buffer-hook, so ediff could use this
hook to auto-delete the ediff-control frame when you delete the
other windows.
Stefan
next prev parent reply other threads:[~2015-05-11 3:27 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 [this message]
2015-05-11 10:08 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvbnhr25yu.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.