Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Trimming .gnus.registry.eieio?
Date: Tue, 19 Feb 2019 17:13:06 -0800	[thread overview]
Message-ID: <87pnrn2rfh.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2lg2b351r.fsf@nwalsh.com>

Norman Walsh <ndw@nwalsh.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> Theoretically, reducing `gnus-registry-max-entries' is what you do to
>> trim it back! What's your value of `gnus-registry-track-extra'? That
>> might contribute to a larger file size.
>
> The relevant settings appear to be:
>
> (setq gnus-registry-max-entries          20000
>       gnus-registry-split-strategy       nil
>       gnus-registry-use-long-group-names t
>       gnus-registry-track-extra          '(recipient))
>
> I’m reasonably sure that gnus-registry-split-fancy-with-parent is the
> only thing I’m using it for. Not sure why I put ‘recipient’ in there.

Well if you're using it for splitting then you probably do want to keep
a slightly larger registry, you never know when you'll get a followup to
an existing message. You can also use `gnus-registry-ignored-groups' to
restrict entry collection to groups you care about.




  reply	other threads:[~2019-02-20  1:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 17:19 Norman Walsh
2019-02-19 19:35 ` Eric Abrahamsen
2019-02-19 20:18   ` Norman Walsh
2019-02-20  1:13     ` Eric Abrahamsen [this message]
2019-02-20  7:39     ` Colin Baxter
2019-02-19 22:40   ` Michael Heerdegen
2019-02-20  1:06     ` Eric Abrahamsen
2019-02-20 15:16     ` Norman Walsh

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=87pnrn2rfh.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).