From: Eric Abrahamsen <email@example.com> To: firstname.lastname@example.org Subject: Re: How about gnus-registry-precious-only-p? Date: Tue, 16 Jun 2020 14:46:06 -0700 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Ted Zlatanov <email@example.com> writes: > On Tue, 16 Jun 2020 11:29:38 -0700 Eric Abrahamsen <firstname.lastname@example.org> 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? Oh, and that would make it even slower because the entries will be constantly recreated if we happen to enter a group multiple times and look at old messages. We could create the full entries when setting marks, but that wouldn't help other packages that might be using the registry to save information. But perhaps we could create a helper function, or an optional CREATE-FULL argument to `gnus-registry-set-id-key'. Will think some more.
next prev parent reply index 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 2020-06-16 21:46 ` Eric Abrahamsen [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Gnus development mailing list Archives are clonable: git clone --mirror http://inbox.vuxu.org/ding Example config snippet for mirrors Newsgroup available over NNTP: nntp://inbox.vuxu.org/vuxu.archive.emacs.gnus.general AGPL code for this site: git clone https://public-inbox.org/public-inbox.git