all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 15183@debbugs.gnu.org
Subject: bug#15183: 24.3.50; emacs_backtrace.txt
Date: Sun, 25 Aug 2013 16:36:24 +0200	[thread overview]
Message-ID: <521A1668.6060004@gmx.at> (raw)
In-Reply-To: <CAAeL0SRRhq1H46JaitpGvkGixrTxKy7xfMZtC-W8kT+OzEwczw@mail.gmail.com>

 > w32_backtrace at w32fns.c:7982
 > emacs_abort at w32fns.c:8014
 > terminate_due_to_signal at emacs.c:369
 > die at alloc.c:6573
 > XWINDOW at lisp.h:799
 > set_window_buffer at window.c:3155
 > delete_frame at frame.c:1251
 > Fdelete_frame at frame.c:1450

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.

Consider choose_minibuf_frame in minibuf.c.  It has a comment which says

       /* I don't think that any frames may validly have a null minibuffer
	 window anymore.  */
       if (NILP (sf->minibuffer_window))
	emacs_abort ();

But on my Emacs I can easily do something like

(let ((frame (make-frame '((minibuffer . nil)))))
   (select-frame frame)
   (minibuffer-window (selected-frame)))

which returns nil.  So the selected frame's minibuffer window slot may
contain nil and unless I'm missing something we have to resolve this
issue first.

martin





  reply	other threads:[~2013-08-25 14:36 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 [this message]
2013-08-25 16:28     ` Drew Adams
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=521A1668.6060004@gmx.at \
    --to=rudalics@gmx.at \
    --cc=15183@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    /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.