From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Re: Trimming .gnus.registry.eieio?
Date: Tue, 19 Feb 2019 14:18:56 -0600 [thread overview]
Message-ID: <m2lg2b351r.fsf@nwalsh.com> (raw)
In-Reply-To: <8736oj4lm9.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 19 Feb 2019 11:35:42 -0800")
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
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.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Those who in their youth did not live
http://nwalsh.com/ | in self-harmony, and who did not gain
| the true treasures of life, are later
| like long-legged old herons standing
| sadly by a lake without fish.--The
| Dhammapada
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-02-19 20:18 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 [this message]
2019-02-20 1:13 ` Eric Abrahamsen
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=m2lg2b351r.fsf@nwalsh.com \
--to=ndw@nwalsh.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).