From: Stefan Kangas <stefan@marxist.se>
To: Alex Bochannek <alex@bochannek.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 49033@debbugs.gnu.org
Subject: bug#49033: 28.0.50; [PATCH] Feature suggestion, url-cache-expiry-alist to override expire time for cache pruning
Date: Sun, 24 Oct 2021 00:27:16 -0700 [thread overview]
Message-ID: <CADwFkmnD3pGRHq5QBSbt7YA1SQ8AJiZZrLX8167A8FA+-VKJJg@mail.gmail.com> (raw)
In-Reply-To: <m2y2b3krcq.fsf@bochannek.com> (Alex Bochannek's message of "Mon, 21 Jun 2021 11:25:09 -0700")
Alex Bochannek <alex@bochannek.com> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Alex Bochannek <alex@bochannek.com> writes:
>>
>>> I originally had looked at this for Gravatar entries and I am now using
>>> it to avoid fetching the same images in RSS feeds.
>>
>> Right; makes sense.
>>
>>> I just noticed though that `url-cache-create-url-from-file' won't work
>>> if `url-cache-create-filename-human-readable' is used. Any suggestions
>>> for how to address that?
>>
>> No, sorry -- I'm pretty unfamiliar with the url-cache code.
>
> I need to think about this some more. The easy way is to not try to
> recreate the URL but to have users specify the path for cache entries. I
> might just do that and see how that works out for me in practice. Either
> way, it's not ready for merging yet.
(That was 17 weeks ago.)
Did you get any further here? Thanks in advance.
next prev parent reply other threads:[~2021-10-24 7:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 5:40 bug#49033: 28.0.50; [PATCH] Feature suggestion, url-cache-expiry-alist to override expire time for cache pruning Alex Bochannek
2021-06-15 14:11 ` Lars Ingebrigtsen
2021-06-15 22:55 ` Alex Bochannek
2021-06-19 12:14 ` Lars Ingebrigtsen
2021-06-19 19:32 ` Alex Bochannek
2021-06-21 12:21 ` Lars Ingebrigtsen
2021-06-21 18:25 ` Alex Bochannek
2021-10-24 7:27 ` Stefan Kangas [this message]
2021-10-27 16:36 ` Alex Bochannek
2021-10-27 16:50 ` Stefan Kangas
2021-06-19 12:56 ` Benjamin Riefenstahl
2021-06-19 19:24 ` Alex Bochannek
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=CADwFkmnD3pGRHq5QBSbt7YA1SQ8AJiZZrLX8167A8FA+-VKJJg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=49033@debbugs.gnu.org \
--cc=alex@bochannek.com \
--cc=larsi@gnus.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).