From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Eli Zaretskii <eliz@gnu.org>, handa@m17n.org, emacs-devel@gnu.org
Subject: Re: image cache
Date: Mon, 15 Dec 2008 15:09:30 -0500 [thread overview]
Message-ID: <jwvy6yhjj9g.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r649ifph.fsf@cyd.mit.edu> (Chong Yidong's message of "Mon, 15 Dec 2008 11:08:26 -0500")
>>>> BTW, does anyone know why each frame has an image cache (even though
>>>> there's really only one image cache per terminal)?
>>> A left-over from before multi-tty?
>> I don't think it's related. The same "problem" was there in Emacs-22,
>> and Emacs-21.
> Note that fixing requires changing all the functions in image.c that
> require a frame argument, so that they use a terminal argument instead.
> Otherwise, if you associate image caches to terminals, you run into
> problems with terminals that have no frame (e.g. terminals created using
> x-open-connection), because you can't supply those image functions with
> a frame argument.
Yes, such a change will/would imply a whole bunch of changes, indeed.
I'm just wondering what is the reason for having chosen frames rather
than terminals when writing the code. Seeing the current state of the
code, it appears that terminals would have been a much more natural
choice, so either I'm missing something, or something has changed which
makes it the natural choice now even tho it wasn't earlier, or the
author had some odd notion of "natural" (or maybe didn't even think
much about it and just chose it arbitrarily).
Stefan
next prev parent reply other threads:[~2008-12-15 20:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 1:26 Memory leak in keyboard variables? Kenichi Handa
2008-12-15 3:16 ` Chong Yidong
2008-12-15 4:06 ` image cache (was: Memory leak in keyboard variables?) Stefan Monnier
2008-12-15 4:12 ` Eli Zaretskii
2008-12-15 15:19 ` image cache Stefan Monnier
2008-12-15 16:08 ` Chong Yidong
2008-12-15 20:09 ` Stefan Monnier [this message]
2008-12-16 1:41 ` Miles Bader
2008-12-16 4:56 ` Chetan Pandya
2008-12-16 7:02 ` Chetan Pandya
2008-12-16 4:31 ` Memory leak in keyboard variables? Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 10:52 Image cache Juri Linkov
2006-02-07 17:21 ` Chong Yidong
2006-02-08 7:22 ` Mathias Dahl
2006-02-08 9:23 ` Juri Linkov
2006-02-14 1:48 ` Juri Linkov
2006-02-07 20:59 ` Stefan Monnier
2006-02-09 17:48 ` Richard M. Stallman
2006-02-09 19:18 ` Juri Linkov
2006-02-09 22:12 ` Chong Yidong
2006-02-09 22:51 ` Mathias Dahl
2006-02-10 0:10 ` Miles Bader
2006-02-10 23:02 ` Richard M. Stallman
2006-02-10 23:21 ` Miles Bader
2006-02-11 1:18 ` Juri Linkov
2006-02-11 2:14 ` Chong Yidong
2006-02-11 21:59 ` Miles Bader
2006-02-12 0:47 ` Stefan Monnier
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=jwvy6yhjj9g.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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.