Gnus development mailing list
 help / color / Atom feed
From: Bob Newell <>
Subject: Re: How about gnus-registry-precious-only-p?
Date: Fri, 12 Jun 2020 04:46:10 -1000
Message-ID: <s6jmu582vgt.fsf@emailmessageidheader.nil> (raw)
In-Reply-To: <> (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

      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
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:

* 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 \ \ \

* 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

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone