From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: How about gnus-registry-precious-only-p?
Date: Tue, 16 Jun 2020 11:29:38 -0700 [thread overview]
Message-ID: <87pn9yc19p.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <k107lyzy.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Fri, 12 Jun 2020 09:04:36 -0700 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> EA> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> I would go further and never record non-precious messages on exiting the
>>> group, to avoid the extra cycles.
>
> EA> I might be misunderstanding, but with the up-thread patch, non-precious
> EA> messages shouldn't be made in the first place. The only way
>
> I misread the patch. Apologies. Looks great to me.
>
> EA> (Which reminds me, now is the right time to come up with a better name
> EA> for this option. Maybe `gnus-registry-auto-create-entries', defaulted to
> EA> nil?)
>
> Yes, I'd be OK with that. Users may have customized
> `gnus-registry-extra-entries-precious' but I think it's unlikely.
Actually, thinking more about it, your point here is important -- it's
probably best to explicitly check the value of
`gnus-registry-extra-entries-precious'. Also, the good thing about
`gnus-registry-register-message-ids' is that it fully populates the
entries with sender, subject, etc. Relying on other manual functions to
create entries may fail to do that, and that information is important to
have.
I'm leaning towards having `gnus-registry-register-message-ids' do its
thing no matter what, and then deleting the entries when leaving the
*Summary* buffer. If the user adds precious data to any of the entries
while in the summary, they won't be deleted.
How does that sound?
next prev parent reply other threads:[~2020-06-16 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 19:47 Eric Abrahamsen
2020-06-09 16:15 ` Ted Zlatanov
2020-06-12 16:04 ` Eric Abrahamsen
2020-06-16 17:08 ` Ted Zlatanov
2020-06-16 18:29 ` Eric Abrahamsen [this message]
2020-06-16 19:08 ` Ted Zlatanov
2020-06-16 21:46 ` Eric Abrahamsen
2020-06-12 14:46 ` Bob Newell
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=87pn9yc19p.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).