From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Don't default to making registry entries for all articles
Date: Sat, 12 Dec 2020 09:06:51 -0800 [thread overview]
Message-ID: <87h7ordkd0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87wny2r40k.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Hi all,
>>
>> I've been thinking about how to do this for a while, and think I've got
>> an okay approach.
>>
>> The Gnus registry registers everything by default, which slows down
>> summary buffer creation, and also saving Gnus. The only time you'd
>> actually want everything registered is if you're splitting using
>> `gnus-registry-split-fancy-with-parent', which I have to imagine is a
>> minority of users.
>>
>> The attached patch lets you change this behavior so the registry only
>> creates and saves entries that you have made manually, either by setting
>> a mark on an article, or via some other library.
>>
>> It does this with a new defcustom, `gnus-registry-register-all-p', which
>> I'd like to default to nil.
>>
>> If this is nil, `gnus-registry-register-message-ids' won't do anything.
>>
>> The patch also adds an optional NO-CREATE argument to
>> `gnus-registry-get-or-make-entry', to tell it to only get, not make.
>> Lastly it has `gnus-registry-get-id-key' set that flag to t, so getting
>> an id key doesn't create a new entry (while setting an id key does).
>
> I suppose a slightly less intrusive approach would be to have
> `gnus-registry-get-id-key' also check the value of
> `gnus-registry-register-all-p', and pass the NO-CREATE flag accordingly.
Okay, this has now gone in. The option is called
`gnus-registry-register-all', and defaults to t to preserve behavior, so
you'll have to set that explicitly if you don't want to save everything.
Eric
next prev parent reply other threads:[~2020-12-12 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 20:15 Eric Abrahamsen
2020-11-30 20:19 ` Eric Abrahamsen
2020-12-12 17:06 ` Eric Abrahamsen [this message]
2020-12-13 3:54 ` 황병희
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=87h7ordkd0.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@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.
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 NNTP newsgroup(s).