all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Sam Steingold <sds@gnu.org>
Cc: 12251@debbugs.gnu.org
Subject: bug#12251: 24.2.50; crash in note_mouse_highlight
Date: Tue, 28 Aug 2012 19:05:09 +0200	[thread overview]
Message-ID: <503CFA45.20001@gmx.at> (raw)
In-Reply-To: <CAFsbZ7Z6Ek=WWxR+KJ+5xMGsuTU1n_W-nydnvP0fQ6EWB55F-w@mail.gmail.com>

 > Debugger entered--Lisp error: (error "#<window 114> is not a live window")
 >   signal(error ("#<window 114> is not a live window"))
 >   error("%s is not a live window" #<window 114>)
 >   window-normalize-window(#<window 114> t)
 >   record-window-buffer(#<window 114>)
 >   set-window-configuration(#<window-configuration>)
 >   ispell-process-line("^report the filtring lift\n" nil)
 >   ispell-region(1 26)
 >   ispell-buffer()
 >   run-hooks(log-edit-done-hook)
 >   log-edit-done()
 >   call-interactively(log-edit-done nil nil)

`set-window-configuration' now has

	  w = XWINDOW (window);
	  if (!NILP (w->buffer)
	      && !EQ (w->buffer, p->buffer)
	      && !NILP (BVAR (XBUFFER (p->buffer), name)))
	    /* If a window we restore gets another buffer, record the
	       window's old buffer.  */
	    call1 (Qrecord_window_buffer, window);

so it's a complete mystery why this fails.  If it happens too
frequently, please take out the

	    call1 (Qrecord_window_buffer, window);

in Fset_window_configuration.  But if you leave it in and the bug
happens again, please try to locate the incriminated window
(`window-tree' could be useful) and tell me whether it's still there and
whether it has a buffer.

Thanks, martin





  reply	other threads:[~2012-08-28 17:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 18:20 bug#12251: 24.2.50; crash in note_mouse_highlight Sam Steingold
2012-08-21 18:42 ` Eli Zaretskii
2012-08-21 19:02   ` Sam Steingold
2012-08-21 19:22     ` Eli Zaretskii
2012-08-22  2:43       ` Sam Steingold
2012-08-22 17:09         ` Eli Zaretskii
2012-08-22 17:29           ` Sam Steingold
2012-08-22 21:12             ` Sam Steingold
2012-08-23  8:48           ` martin rudalics
2012-08-23 13:19             ` Sam Steingold
2012-08-23 17:18               ` martin rudalics
2012-08-24 20:33                 ` Sam Steingold
2012-08-25 13:40                   ` martin rudalics
2012-08-27 19:01                     ` Sam Steingold
2012-08-27 19:05                       ` Sam Steingold
2012-08-27 21:10                         ` martin rudalics
2012-08-28 16:35                         ` Sam Steingold
2012-08-28 17:05                           ` martin rudalics [this message]
2012-08-29  9:34                             ` martin rudalics
2012-08-29 14:42                               ` Sam Steingold
2012-08-30  8:03                                 ` martin rudalics
2012-08-30 11:02                                   ` Sam Steingold
2012-09-01  9:36                                     ` Eli Zaretskii
2012-09-05 19:56                                       ` Sam Steingold
2012-09-06  2:31                                         ` Sam Steingold
2012-09-06  3:13                                           ` Sam Steingold
2012-09-06  5:15                                           ` Werner LEMBERG
2012-09-06  5:04                                         ` Eli Zaretskii
2012-09-06  7:20                                         ` martin rudalics
2012-09-06  7:32                                           ` martin rudalics
2012-08-30 12:39                                   ` Sam Steingold
2012-08-30 12:49                                     ` martin rudalics
2012-09-01  9:40               ` Eli Zaretskii
2012-08-23 16:20             ` Eli Zaretskii
2012-08-23 17:19               ` martin rudalics
2012-08-23 18:43                 ` Eli Zaretskii
2012-08-24  9:44                   ` 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=503CFA45.20001@gmx.at \
    --to=rudalics@gmx.at \
    --cc=12251@debbugs.gnu.org \
    --cc=sds@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.