From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: Doc bug: gnus-registry-ignored-groups, gnus-registry-unfollowed-groups, nnmail-split-fancy-with-parent-ignore-groups
Date: Wed, 10 Jan 2007 01:26:28 +0100 [thread overview]
Message-ID: <v91wm3rakr.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <g69d55nkhi5.fsf@dhcp-65-162.kendall.corp.akamai.com> (Ted Zlatanov's message of "Tue\, 09 Jan 2007 16\:38\:42 -0500")
[ Adding ding ... ]
On Tue, Jan 09 2007, Ted Zlatanov wrote:
> On 9 Jan 2007, kai.grossjohann@de.verizonbusiness.com wrote:
>
>> gnus.el defines the variable gnus-registry-ignored-groups, but this
>> variable is never referenced in the code (except in one comment in
>> gnus-registry.el).
>
> Do you want to write a patch to use that variable? I haven't had the
> time to implement it, but I do think it could be useful. It's not
> intended to be the same as g-r-unfollowed-groups, which just affects
> gnus-registry-split-fancy-with-parent.
>
>> Code in gnus-registry.el references the variable
>> nnmail-split-fancy-with-parent-ignore-groups, but this fact isn't
>> documented.
>
> Fixed.
Could you please apply the doc fixes in v5-10 as well, if appropriate?
>> The documentation of gnus-registry-unfollowed-groups seems unclear to
>> me. I think it means "never split a message into one of these groups,
>> even if the registry says it should be put there". (I'll try that
>> next to see whether I can avoid splitting messages into the group
>> nnimap+foo:INBOX.makeham. I have a script to train bogofilter on that
>> group and to move the messages to INBOX, and then splitting promptly
>> moves them back to INBOX.makeham...)
>
> Fixed. The docs are correct, let's see if the behavior works for you
> :) Let me know if the docs are still unclear.
>
> Good to see you back, btw.
AOL! :-)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2007-01-10 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86zm8smand.fsf@ketchup.de.uu.net>
[not found] ` <g69d55nkhi5.fsf@dhcp-65-162.kendall.corp.akamai.com>
2007-01-10 0:26 ` Reiner Steib [this message]
2007-01-10 15:57 ` Ted Zlatanov
2007-01-10 21:48 ` Reiner Steib
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=v91wm3rakr.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+from-uce@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).