From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: How about gnus-registry-precious-only-p?
Date: Fri, 12 Jun 2020 04:46:10 -1000 [thread overview]
Message-ID: <s6jmu582vgt.fsf@emailmessageidheader.nil> (raw)
In-Reply-To: <87blmifkxe.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 20 May 2020 12:47:25 -0700")
> It occurred to me that if you're not using the Gnus registry's
> split-with-parent functionality, there really isn't any need to let it
> bloat up with thousands of entries.
I must agree! For months and months I fought registry bloat
with little luck. Eventually some patches and fixes came in
(thank you Eric!) but it still was more than I wanted.
So I went to a system such as what Eric has suggested. Now the
registry has a small handful of entries that really matter and
it actually serves a useful purpose.
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
prev parent reply other threads:[~2020-06-12 14:47 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
2020-06-16 21:46 ` Eric Abrahamsen
2020-06-12 14:46 ` Bob Newell [this message]
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=s6jmu582vgt.fsf@emailmessageidheader.nil \
--to=bobnewell@bobnewell.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).