unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: 9310-done@debbugs.gnu.org
Subject: bug#9310: BadWindow error with quail guidance frame
Date: Fri, 14 Oct 2011 13:46:57 -0400	[thread overview]
Message-ID: <jwvzkh3zcul.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4E54FD6B.10700@swipnet.se> (Jan D.'s message of "Wed, 24 Aug 2011 15:32:27 +0200")

>>> Basically set synchronized and break in the error function.
>> OK, that part was already done.
>>> Then go up the call stack to find the frame the window belongs to,
>> That as well: it's the minibuffer-only frame.
>>> or see if it is some uninitialized value.
>> Doesn't look like it, the frames involved seem to have sensible
>> field values.  This problem started around the time the new window.c code
>> was installed, FWIW (which doesn't mean it's actually related).
> You can try xwininfo -id <the window> to see if there is something special
> about that window.  Compare with another window you have in Emacs.

Nothing stands out, no.  I just installed a patch that ignores errors in
that XSetWindowBorder function and it seems to be sufficient.


        Stefan





      reply	other threads:[~2011-10-14 17:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 20:15 bug#9310: BadWindow error with quail guidance frame Stefan Monnier
2011-08-17  6:03 ` Jan D.
2011-08-17 13:46   ` Stefan Monnier
2011-08-17 16:39     ` Jan Djärv
2011-08-17 21:45       ` Chong Yidong
2011-08-23  2:23       ` Stefan Monnier
2011-08-23  6:17         ` Jan D.
2011-08-23 19:40           ` Stefan Monnier
2011-08-24 13:32             ` Jan D.
2011-10-14 17:46               ` Stefan Monnier [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvzkh3zcul.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=9310-done@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).