all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, Juanma Barranquero <lekktu@gmail.com>
Cc: 15183@debbugs.gnu.org
Subject: bug#15183: 24.3.50; emacs_backtrace.txt
Date: Sun, 25 Aug 2013 09:28:23 -0700 (PDT)	[thread overview]
Message-ID: <79502512-9512-430e-8358-b9e04cdd3f9b@default> (raw)
In-Reply-To: <521A1668.6060004@gmx.at>

In case it helps, let me repeat what I wrote at the outset for this bug:
this crash came from a session started with `emacs -Q', *not* from my
setup (so no standalone minibuffer etc.).

I do not recall the actions I took after `emacs -Q', but the crash
occurred very soon after starting Emacs.

It might have been after testing this (for another user), but I don't
want to mislead you because I really do not recall:

(defadvice ediff-buffers (around pop-up-frames activate)
  "Use non-nil `pop-up-frames'."
  (let ((pop-up-frames  t))
    ad-do-it))

The point is that I did not load *any* of my libraries in the session,
IIRC.

> So IIUC when Drew calls `delete-frame' either (1) the selected frame
> does not have a minibuffer or (2) the frame to be deleted was selected
> and the frame selected instead doesn't have a minibuffer.  I'm not yet
> sure what to do but am afraid there's some basic misunderstanding here.





  reply	other threads:[~2013-08-25 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25  1:01 bug#15183: 24.3.50; emacs_backtrace.txt Drew Adams
2013-08-25  1:51 ` Juanma Barranquero
2013-08-25 14:36   ` martin rudalics
2013-08-25 16:28     ` Drew Adams [this message]
2013-08-25 17:31       ` martin rudalics
2013-08-25 17:49         ` Eli Zaretskii
2013-08-26 13:06           ` martin rudalics
2013-08-26 13:34             ` Eli Zaretskii

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=79502512-9512-430e-8358-b9e04cdd3f9b@default \
    --to=drew.adams@oracle.com \
    --cc=15183@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=rudalics@gmx.at \
    /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.