all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Tue, 12 May 2015 11:36:24 +0200	[thread overview]
Message-ID: <5551C998.4040508@gmx.at> (raw)
In-Reply-To: <57556.25510.62959.21840@gargle.gargle.HOWL>

 > My usage scenario is the following:
 >
 > Normally I run emacs with always no more than two frames.  I create
 > a 2nd frame as needed, but I delete it when it is not needed anymore
 > so that it does not clutter the desktop.  An ediff session then adds
 > one more frame for the ediff control panel.  Yet during an ediff
 > session I can get side-tracked: the frame used for displaying the ediff
 > buffers A and B may get used for something else, then I create
 > another frame and finally I want to delete the frame that Ediff
 > wants to use as surrogate minibuffer frame.

Such things happen to me all the time.  That's why I prefer
`ediff-setup-windows-plain' (and `split-window-horizontally' as
`ediff-split-window-function').

 > I understand that the frame displaying the ediff control panel needs
 > *some* other frame to provide a minibuffer.  Is it necessary that a
 > particular frame serves this purpose?  Or would it be sufficient
 > that emacs made sure that always at least one frame has a proper
 > minibuffer?  (In the case of the ediff control panel, I believe it
 > is fair to assume that anyway this frame rarely requires a proper
 > minibuffer. For me, the control panel is effectively the minibuffer
 > for an ediff session: commands are entered in that buffer; there is
 > no need for "a minibuffer for the ediff minibuffer".)

At any time every frame has a corresponding minibuffer window and that
window won't change for the frame's entire lifetime.

 > If nothing else, it would be good if the error message issued when
 > attempting to delete a surrogate minibuffer frame could be improved:
 > I got this error message at a point when I was not thinking about
 > ediff, but I just wanted to get back to my default "one frame
 > setup"; and it happened I wanted to delete the wrong frame to
 > achieve this goal.

The problem is that the entity that issues the message is not aware of
the intrinsics of ediff.

martin





  reply	other threads:[~2015-05-12  9:36 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
2015-05-11 17:03       ` Roland Winkler
2015-05-12  9:36         ` martin rudalics [this message]
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=5551C998.4040508@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 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.