unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: rms@gnu.org, "Károly Lőrentey" <Karoly.Lorentey@cern.ch>,
	emacs-devel@gnu.org
Subject: Re: x-create-frame is sluggish
Date: Mon, 11 Oct 2004 22:03:00 +0200	[thread overview]
Message-ID: <8D30AFB5-1BC0-11D9-90CA-000D93505B76@swipnet.se> (raw)
In-Reply-To: <E6087AA0-1BBE-11D9-B381-000D93505B76@swipnet.se>

>
>> +   /* See if there is another frame already using same fontset. */
>> +   FOR_EACH_FRAME (rest, frame)
>> +     {
>> +       struct frame *cf = XFRAME (frame);
>> +       if (cf != f && FRAME_LIVE_P (f) && FRAME_X_P (cf)
>> +           && FRAME_X_DISPLAY_INFO (cf) == FRAME_X_DISPLAY_INFO (f)
>> +           && !strcmp (FRAME_XIC_BASE_FONTNAME (cf), base_fontname))
>> +         return FRAME_XIC_FONTSET (cf);
>
> You should use FRAME_X_DISPLAY, not FRAME_X_DISPLAY_INFO everywhere.
> A frame can be opened on display ":0", "unix:0", "hostname:0" and so 
> on,
> but it is still the same display.  However, they will have different 
> display info.

To correct myself,  FRAME_X_DISPLAY_INFO is fine, don't know what I was
thinking.

	Jan D.

  reply	other threads:[~2004-10-11 20:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 14:15 x-create-frame is sluggish Lőrentey Károly
2004-09-24 12:08 ` Richard Stallman
2004-09-25  2:39 ` Kenichi Handa
2004-09-25 15:36   ` Richard Stallman
2004-10-01  1:26     ` Kenichi Handa
2004-10-01  8:51       ` Károly Lőrentey
2004-10-10 22:45         ` Lőrentey Károly
2004-10-11  7:54           ` Jan D.
2004-10-11 14:53             ` Károly Lőrentey
2004-10-11 19:51               ` Jan D.
2004-10-11 20:03                 ` Jan D. [this message]
2004-10-25 13:07               ` Lőrentey Károly
2004-10-25 13:16                 ` Jan D.
2004-10-03 14:32       ` Richard Stallman

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=8D30AFB5-1BC0-11D9-90CA-000D93505B76@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=Karoly.Lorentey@cern.ch \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).