Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: How about gnus-registry-precious-only-p?
Date: Tue, 16 Jun 2020 19:08:08 +0000	[thread overview]
Message-ID: <tuzaltgn.fsf@lifelogs.com> (raw)
In-Reply-To: <87pn9yc19p.fsf@ericabrahamsen.net>

On Tue, 16 Jun 2020 11:29:38 -0700 Eric Abrahamsen <eric@ericabrahamsen.net> wrote: 

EA> Actually, thinking more about it, your point here is important -- it's
EA> probably best to explicitly check the value of
EA> `gnus-registry-extra-entries-precious'. Also, the good thing about
EA> `gnus-registry-register-message-ids' is that it fully populates the
EA> entries with sender, subject, etc. Relying on other manual functions to
EA> create entries may fail to do that, and that information is important to
EA> have.

EA> I'm leaning towards having `gnus-registry-register-message-ids' do its
EA> thing no matter what, and then deleting the entries when leaving the
EA> *Summary* buffer. If the user adds precious data to any of the entries
EA> while in the summary, they won't be deleted.

OK. For large groups, this gets slow in my experience. Could we register
the articles when adding the marks or when leaving the summary?

Ted



  reply	other threads:[~2020-06-16 19:08 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
2020-06-16 19:08         ` Ted Zlatanov [this message]
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=tuzaltgn.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).