From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, gerd@gnu.org
Subject: Re: [patch] cache color info for remote X sessions [Was: Emacs 21/X11 generating unbelieveable network traffic]
Date: Mon, 07 Oct 2002 11:31:04 -0400 [thread overview]
Message-ID: <E17yZqa-0006GG-00@fencepost.gnu.org> (raw)
In-Reply-To: <m3d6qoct7n.fsf@fischman.org> (message from Ami Fischman on Sat, 05 Oct 2002 17:21:48 -0700)
Another obvious thing to cache would be the font data that emacs can
request, although it is much less clear to me how to cache the XExtData
list that is potentially contained in an XFontStruct (namely, how do you
know how big the private data is? If anyone has any suggestions here, I'd
like to hear them).
Maybe the thing to do is to copy and cache just the data that Emacs
actually looks at in that code.
For fonts that are actually being used for display, Emacs already has
a cache. So I suspect (though I'm partly guessing) that this is for
some other part of Emacs which is just thinking about fonts and not
actually using them. If that is true, I suspect that the parts of the
font data it uses are rather limited.
prev parent reply other threads:[~2002-10-07 15:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 0:21 [patch] cache color info for remote X sessions [Was: Emacs 21/X11 generating unbelieveable network traffic] Ami Fischman
2002-10-06 1:29 ` Miles Bader
2002-10-06 5:31 ` Ami Fischman
2002-10-06 6:53 ` Miles Bader
2002-10-06 17:59 ` Jan D.
2002-10-06 20:22 ` Ami Fischman
2002-10-06 18:14 ` Ami Fischman
2002-10-07 14:53 ` Stefan Monnier
2002-10-07 15:35 ` Ami Fischman
2002-10-07 15:52 ` Stefan Monnier
2002-10-07 16:49 ` Ami Fischman
2002-10-07 17:59 ` Jan D.
2002-10-07 18:14 ` Jan D.
2002-10-07 20:07 ` Stefan Monnier
2002-10-08 5:16 ` Jan D.
2002-10-08 17:21 ` Richard Stallman
2002-10-07 15:31 ` Richard Stallman
2002-10-07 17:04 ` Ami Fischman
2002-10-08 17:21 ` Richard Stallman
2002-10-06 7:46 ` Jan D.
2002-10-06 17:33 ` Ami Fischman
2002-10-07 15:31 ` Richard Stallman [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=E17yZqa-0006GG-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd@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).