[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: |
Thu, 17 Oct 2024 11:51:08 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi,
I'm trying to revisit this idea of having a user controlled image cache.
The goal is to have, for instance, image-mode use it because (hopefully)
it would have a better idea of when to cache/uncache images for its
usage.
Here is a patch of such a prototype « user image cache ».
For the moment, I wanted to keep it minimal so the only interface to use
it goes as follow. When a user (or a program) use the image attribute
":ttl TIME_IN_SECONDS" with `create-image' such image will be stored in
the « user cache » and not in the internal one. Images lookups use both
caches (internal and internal, in that order). A negative
TIME_IN_SECONDS means « cache this image forever ».
I think there will be a need for user function that completely flushes
the images in this new cache. But do you think we need others commands
for such interface?
0001-User-controlled-image-cache.patch
Description: Text Data
--
Manuel Giraud
- bug#68006: 30.0.50; Image-mode speed,
Manuel Giraud <=
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/10/19
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/10/21
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/10/21
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/10/21
- bug#68006: 30.0.50; Image-mode speed, Eli Zaretskii, 2024/10/21
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/10/22
- bug#68006: 30.0.50; Image-mode speed, Manuel Giraud, 2024/10/28