From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alex Bochannek <alex@bochannek.com>
Cc: 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: Sat, 19 Jun 2021 14:14:47 +0200 [thread overview]
Message-ID: <877diq2gqw.fsf@gnus.org> (raw)
In-Reply-To: <m2czsmagat.fsf@bochannek.com> (Alex Bochannek's message of "Tue, 15 Jun 2021 15:55:54 -0700")
Alex Bochannek <alex@bochannek.com> writes:
> I tend to find it difficult to reason about functionality if constants
> like this are in the code and not in variables. It may be unlikely that
> many people will want to customize it, but I'd rather expose this as a
> configuration variable than hide a static value in the code.
Adding user options to control things nobody has asked about isn't
helpful.
> Support URL-specific cache expiration
>
> * test/lisp/url/url-cache-tests.el: Test URL-to-filename and
> filename-to-URL mappings used by URL caching.
>
> * lisp/url/url-cache.el (url-cache-expiry-alist)
> (url-cache-create-url-from-file, url-cache-expired)
> (url-cache-prune-cache): Expire cache entries based on regular
> expressions matching URLs defined in new customizable variable
> url-cache-expire-alist.
>
> * doc/misc/url.texi (Disk Caching): Mention
> url-cache-expiry-alist variable.
Looks good to me. What's the use case for this, though?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-06-19 12:14 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877diq2gqw.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=49033@debbugs.gnu.org \
--cc=alex@bochannek.com \
/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.