Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: gnus-registry-ignored-groups (was: gnus-registry question)
Date: Wed, 19 Nov 2003 16:01:56 -0500	[thread overview]
Message-ID: <4nbrr8dqd7.fsf_-_@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <u4qx8camn.fsf@adobe.com> (Danny Siu's message of "Thu, 13 Nov 2003 11:49:04 -0800")

OK, here's the straight answer to gnus-registry-ignored-groups:

I had forgotten about it, and my comment was wrong.  It is indeed
used.

gnus-registry-ignored-groups is used when deciding if a group name
should be stored at all.  There's also a registry-ignore group
parameter that will do the same thing.

gnus-registry-unfollowed-groups and
nnmail-split-fancy-with-parent-ignore-groups are used when we get a
group name, and decide if we should give it back.  So the *ignored*
groups never get in the registry, while the *unfollowed* groups are
filtered out.

This is actually a meaningful difference.  Registry entries currently
get deleted when there are no more groups associated with them.
Thus, if you value the registry information about articles in a
group, you'd use gnus-registry-unfollowed-groups.  If you never want
to hear about articles in a group, you'd use
gnus-registry-ignored-groups.

nnmail-split-fancy-with-parent-ignore-groups has an unfortunately
confusing name.  It is analogous to gnus-registry-unfollowed-groups.

The above will *definitely* go in the manual.  Sorry for the confusion!

Ted



      reply	other threads:[~2003-11-19 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 21:41 gnus-registry question Jake Colman
2003-11-12 22:04 ` Ted Zlatanov
2003-11-14 13:25   ` Jake Colman
2003-11-19 21:06     ` Ted Zlatanov
2003-11-12 23:07 ` Danny Siu
2003-11-13 15:50   ` Jake Colman
2003-11-13 16:57   ` Ted Zlatanov
2003-11-13 19:13     ` Raymond Scholz
2003-11-13 19:49     ` Danny Siu
2003-11-19 21:01       ` Ted Zlatanov [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=4nbrr8dqd7.fsf_-_@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    /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).