From: Tassilo Horn <tsdh@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: Some Gnus Registry questions
Date: Mon, 10 Jun 2013 08:55:54 +0200 [thread overview]
Message-ID: <87k3m2ihdx.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m2bo7eegue.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
Hi Ted,
> TH> 2) The default value of `gnus-registry-track-extra' is (subject sender
> TH> recipient). When looking at the gnus registry eioio file, I can see
> TH> that especially the subject tracking is responsible for a very large
> TH> portion. Now the question is: do I actually need that?
>
> Probably no, if you never search by subject.
I sometimes search by subject, but then it's with nnir on nnimap
groups.
> If you split by subject with the registry, then yes.
>
> TH> I don't use client-side splitting, so I think the only position where
> TH> I use the registry is for referring articles (^) and gathering
> TH> threads (A T), right? And since I also use
>
> TH> (setq gnus-summary-thread-gathering-function
> TH> 'gnus-gather-threads-by-references)
>
> TH> I probably don't need the registry tracking subjects, right?
>
> Correct. I wonder if it could figure this out automatically.
>
> TH> In the same sense, do I actually need sender and recipient tracking?
> TH> For article referring and thread gathering, I think only the
> TH> Message-Id is needed, right?
>
> Correct.
Thanks for the confirmation!
Bye,
Tassilo
next prev parent reply other threads:[~2013-06-10 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.23938.1365663121.855.info-gnus-english@gnu.org>
2013-06-10 4:21 ` Ted Zlatanov
2013-06-10 6:55 ` Tassilo Horn [this message]
2013-06-13 6:08 ` Tassilo Horn
[not found] ` <mailman.1516.1371103738.22516.info-gnus-english@gnu.org>
2013-06-16 9:17 ` Ted Zlatanov
2013-07-03 8:07 ` Tassilo Horn
[not found] ` <mailman.116.1372838844.12400.info-gnus-english@gnu.org>
2013-07-08 12:15 ` Ted Zlatanov
2013-04-11 6:51 Tassilo Horn
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=87k3m2ihdx.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=info-gnus-english@gnu.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).