From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 45033@debbugs.gnu.org
Subject: bug#45033: 28.0.50; New option gnus-registery-register-all-p
Date: Fri, 04 Dec 2020 11:11:12 +0100 [thread overview]
Message-ID: <87blf9nanz.fsf@gnus.org> (raw)
In-Reply-To: <87tut24ej3.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 03 Dec 2020 16:10:24 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> This patch introduces a new customization option,
> `gnus-registry-register-all-p', which, when nil, won't create database
> entries automatically. The registry will only contain entries that the
> user (or other packages) has created manually. If the user isn't using
> automatic splitting, this can provide a significant speedup for general
> Gnus usage.
Makes sense to me. However, the option shouldn't have a name ending in
-p -- that's for predicate functions only. `gnus-registry-register-all'
would be a better name.
> Discussions on gnus.general lead me to believe that universal splitting
> isn't used all that often, and that most users are very surprised to
> find that they have a 50MB registry file on disk. Therefore I've
> defaulted this option to nil, which is a change from previous behavior.
> It would be perfectly easy to default to t if this seems inappropriate.
I think defaulting it to t makes more sense (besides being more
backwards-compatible) -- the registry isn't on by default, after all.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-04 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 0:10 bug#45033: 28.0.50; New option gnus-registery-register-all-p Eric Abrahamsen
2020-12-04 10:11 ` Lars Ingebrigtsen [this message]
2020-12-04 17:35 ` Eric Abrahamsen
2020-12-11 17:17 ` Eric Abrahamsen
2020-12-12 11:00 ` Lars Ingebrigtsen
2020-12-12 17:07 ` Eric Abrahamsen
2020-12-18 23:16 ` Basil L. Contovounesios
2020-12-19 18:04 ` Eric Abrahamsen
2020-12-19 23:25 ` Eric Abrahamsen
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=87blf9nanz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45033@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
/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.