[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#68006: 30.0.50; Image-mode speed
From: |
Manuel Giraud |
Subject: |
bug#68006: 30.0.50; Image-mode speed |
Date: |
Fri, 05 Jan 2024 15:54:53 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Manuel Giraud <manuel@ledu-giraud.fr>
>> Cc: stefankangas@gmail.com, 68006@debbugs.gnu.org
>> Date: Fri, 05 Jan 2024 15:35:42 +0100
>>
>> I also imagine it would be mostly in C. But looking at the code, I
>> think I have overlooked something: lookup_image is what currently does
>> most of the work (with caching) and this is in called in many places in
>> "xdisp.c". Of course, I think we should keep that... but then how could
>> we design this new cache?
>
> For example, lookup_image could look in both the existing and this new
> cache.
Yes why not. So your idea is to have just one more other cache that we
can access differently than the current one. I was thinking more of
something to let Lisp programs create their own image cache but that may
be less practical.
--
Manuel Giraud
- bug#68006: 30.0.50; Image-mode speed, (continued)
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/01/04
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/01/04
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/01/04
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/01/04
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/01/05
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/01/05
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/01/05
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/01/05
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/01/05
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/01/05
- bug#68006: 30.0.50; Image-mode speed,
Manuel Giraud <=
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/01/06