all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Roland Winkler <winkler@gnu.org>, martin rudalics <rudalics@gmx.at>
Cc: 20538@debbugs.gnu.org
Subject: bug#20538: 24.4; Attempt to delete a surrogate minibuffer frame
Date: Sun, 10 May 2015 13:17:43 -0700 (PDT)	[thread overview]
Message-ID: <0efbad77-3f61-46d9-8092-5db1bec27c3b@default> (raw)
In-Reply-To: <46510.69799.372989.21839@gargle.gargle.HOWL>

> 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

I was going to guess that it had something to do with having
one of the compared buffers in a separate frame, i.e., two
frames showing a buffer being compared.

That's been problematic all along, AFAIK.  It can make Ediff
tremble in the knees.  Especially if you do something like this:

> M-x delete-frame

That kind of thing can also result in Ediff screaming that
you've killed one of its relatives.





  reply	other threads:[~2015-05-10 20:17 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 [this message]
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
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=0efbad77-3f61-46d9-8092-5db1bec27c3b@default \
    --to=drew.adams@oracle.com \
    --cc=20538@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --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.