From: Ken Raeburn <raeburn@permabit.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21473@debbugs.gnu.org
Subject: bug#21473: 24.5; very slow tooltip display to sort-of-slow remote display
Date: Tue, 29 Sep 2015 16:15:59 -0400 [thread overview]
Message-ID: <CAJJWxE8J5Y6R8X_nV+JFM5L5fV-uiW7cYbyLe3zNdbeA++3PVQ@mail.gmail.com> (raw)
In-Reply-To: <BB52C645-1B8C-499F-87DE-FA960C6E438A@permabit.com>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
I'm working on some experimental patches to implement caching of color-name
lookups and color-cell allocations.
Along the way I noticed that for visual class TrueColor, we never free
color cells on the server, and we can (and do, but only in image.c)
synthesize pixel values from RGB values instead of calling XAllocColor and
making the round trip to the server. TrueColor is all my laptop display
supports, and I gather it's supported on most hardware these days, so it
may be worth taking advantage of these to cut out the extra traffic, and I
can probably drop the color-cell allocation cache work...
Ken
[-- Attachment #2: Type: text/html, Size: 688 bytes --]
next prev parent reply other threads:[~2015-09-29 20:15 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
2015-09-27 13:29 ` Ken Raeburn
2015-09-29 20:15 ` Ken Raeburn [this message]
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
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=CAJJWxE8J5Y6R8X_nV+JFM5L5fV-uiW7cYbyLe3zNdbeA++3PVQ@mail.gmail.com \
--to=raeburn@permabit.com \
--cc=21473@debbugs.gnu.org \
--cc=eliz@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).