From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: gnus-registry question
Date: Thu, 13 Nov 2003 11:57:45 -0500 [thread overview]
Message-ID: <4n8ymk8auu.fsf@benko.bwh.harvard.edu> (raw)
In-Reply-To: <uislp89uz.fsf@adobe.com> (Danny Siu's message of "Wed, 12 Nov 2003 15:07:00 -0800")
On Wed, 12 Nov 2003, dsiu@adobe.com wrote:
> I Gcc all my replies to "Archive" groups and the group that it is
> originated. I use gnus-registry-split-fancy-with-parent and have
> added my "Archive" groups to gnus-registry-ignored-groups. All the
> followups seem to land into the correct mail box
>
> (setq gnus-registry-ignored-groups '(("nnrss" t)
> ("nntp" t)
> ("spam" t)
> ("Archive" t)))
Are you sure you don't mean gnus-registry-unfollowed-groups (default
is '("delayed" "drafts" "queue"))? I can't find
gnus-registry-ignored-groups in my code :)
gnus-registry.el also respects
nnmail-split-fancy-with-parent-ignore-groups.
Both of the variables above are actually lists of strings to be
matched, not association lists as you indicate.
I think the list you indicate would actually be good for general use
as a default, with a slight modification:
(setq gnus-registry-unfollowed-groups '("delayed" "drafts" "queue"
"^nnrss:" "^nntp:" "spam"))
;; untested
(when (featurep 'spam)
(dolist (group spam-junk-mailgroups)
(add-to-list gnus-registry-unfollowed-groups group)))
What do you think of the above as a default? The ^ anchor is needed
because otherwise groups like "nnml:discuss-nntp" would be matched.
Thanks
Ted
next prev parent reply other threads:[~2003-11-13 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 21:41 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 [this message]
2003-11-13 19:13 ` Raymond Scholz
2003-11-13 19:49 ` Danny Siu
2003-11-19 21:01 ` gnus-registry-ignored-groups (was: gnus-registry question) Ted Zlatanov
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=4n8ymk8auu.fsf@benko.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).