From: Chong Yidong <cyd@stupidchicken.com>
To: Jose Antonio Ortega Ruiz <jaortega@gmail.com>
Cc: 3194@emacsbugs.donarmstrong.com, rfrancoise@debian.org
Subject: bug#3194: 23.0.93; Error opening X frame when it's named
Date: Wed, 06 May 2009 20:09:01 -0400 [thread overview]
Message-ID: <87d4alhizm.fsf@cyd.mit.edu> (raw)
In-Reply-To: <873abmf7g5.fsf@mithrandir.homeunix.net> (Jose Antonio Ortega Ruiz's message of "Sun, 03 May 2009 18:59:54 +0200")
Jose Antonio Ortega Ruiz <jaortega@gmail.com> writes:
> The *first* time I try, it works; but subsequent re-evaluations (after
> closing the initial frame), fail with the error i reported. Could this
> be your case too?
OK, I see the problem. This is a loophole in the frame creating
logic---we usually rely on x-create-frame to open the X connection if
it's not already open, but for named faces we need the X resources
associated with the face name. So x-handle-named-frame-geometry really
ought to open the X connection. The reason this does not happen for the
first X frame is that we detect that specially, and open the X
connection for initializing the various graphical settings.
I don't want to make any changes to the logic at this stage of the
pretest, so I've installed a temporary workaround, which ignores the
error in x-handle-named-frame-geometry. This has one drawback: any
special X resources you associate with that frame name are not
recognized.
I'll keep this bug open, and look into a more comprehensive solution
after the release.
next prev parent reply other threads:[~2009-05-07 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 15:17 bug#3194: 23.0.93; Error opening X frame when it's named Chong Yidong
2009-05-03 16:59 ` Jose Antonio Ortega Ruiz
2009-05-07 0:09 ` Chong Yidong [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-02 19:09 Jose Antonio Ortega Ruiz
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=87d4alhizm.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=3194@emacsbugs.donarmstrong.com \
--cc=jaortega@gmail.com \
--cc=rfrancoise@debian.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.