From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@permabit.com>
Cc: 21473@debbugs.gnu.org
Subject: bug#21473: 24.5; very slow tooltip display to sort-of-slow remote display
Date: Sun, 27 Sep 2015 13:38:24 +0300 [thread overview]
Message-ID: <83612wf8pr.fsf@gnu.org> (raw)
In-Reply-To: <59C0A752-87BB-4467-9A3F-DC1E5A278842@permabit.com>
> From: Ken Raeburn <raeburn@permabit.com>
> Date: Sun, 27 Sep 2015 06:35:30 -0400
> Cc: 21473@debbugs.gnu.org
>
> This one’s still basically unchanged. I just got 165 _XReply round-trip delays, with face realization color requests accounting for 60 of those, x_create_tip_frame initialization using “black” and “white” accounting for a dozen more, and other XParseColor or XAllocColor calls bringing it up to around 100 (maybe fewer than last time, by just a few); 38 XSync calls, almost all for error catching. The other ~20% is XQueryColors, XListFonts, XGetWindowProperty, and a few other calls that need responses.
So you are saying that creating a tip frame is significantly different
in this regard from creating any "regular" frame? If so, where are
the differences, wrt face realization and color allocation?
next prev parent reply other threads:[~2015-09-27 10:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 8:13 bug#21473: 24.5; very slow tooltip display to sort-of-slow remote display Ken Raeburn
2015-09-15 14:32 ` Eli Zaretskii
2015-09-15 22:03 ` Ken Raeburn
2015-09-26 7:03 ` Eli Zaretskii
2015-09-27 10:35 ` Ken Raeburn
2015-09-27 10:38 ` Eli Zaretskii [this message]
2015-09-27 13:29 ` Ken Raeburn
2015-09-29 20:15 ` Ken Raeburn
2015-09-30 7:23 ` Eli Zaretskii
2015-10-01 10:01 ` Ken Raeburn
2015-10-01 16:51 ` Ken Raeburn
2015-10-04 9:45 ` Eli Zaretskii
2015-10-04 18:02 ` Ken Raeburn
2015-10-04 19:40 ` Eli Zaretskii
2015-10-05 5:38 ` Ken Raeburn
2015-10-05 6:25 ` Eli Zaretskii
2015-10-06 2:15 ` Ken Raeburn
2015-10-06 2:44 ` Eli Zaretskii
2015-10-06 9:30 ` Ken Raeburn
2015-10-06 14:46 ` Eli Zaretskii
2015-10-07 6:09 ` Ken Raeburn
2015-10-07 15:31 ` Eli Zaretskii
2015-10-08 6:04 ` Ken Raeburn
2015-10-08 8:12 ` Ken Raeburn
2021-09-19 22:29 ` Stefan Kangas
2022-04-24 13:19 ` Lars Ingebrigtsen
2022-04-25 2:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 8:02 ` Lars Ingebrigtsen
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=83612wf8pr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21473@debbugs.gnu.org \
--cc=raeburn@permabit.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.