From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Split based on threads?
Date: Thu, 24 Jun 2004 16:43:36 +0200 [thread overview]
Message-ID: <v9d63p819j.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <86oen9ox9y.fsf@rumba.de.uu.net>
Kai Grossjohann <kai@emptydomain.de> writes:
[ nnmail-split-fancy-with-parent
vs. gnus-registry-split-fancy-with-parent ]
> But the real limitation (that has been lifted with gnus-registry) is
> that nnmail-split-fancy-with-parent is restricted to the "primary
> mail backend". If gnus-select-method is a mail backend, then that's
> it, and otherwise gnus-secondary-select-methods is searched in order
> for the first mail backend, which becomes the "primary mail backend".
>
> nnmail-split-fancy-with-parent should be removed from Gnus, I think.
>
> WDYT?
I didn't try `gnus-registry' yet, because I'm quite happy with
`nnmail-split-fancy-with-parent' upto now. Is
`gnus-registry-split-fancy-with-parent' a drop-in replacement for
`nnmail-split-fancy-with-parent' (after initialization)?
Once `gnus-registry' is properly documented in the manual, we could at
least describe `nnmail-split-fancy-with-parent' as obsolete an refer
to `gnus-registry-split-fancy-with-parent'.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-06-24 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 20:12 Norman Walsh
2004-06-18 21:17 ` Chris Green
2004-06-18 22:49 ` Jesper Harder
2004-06-21 14:39 ` Ted Zlatanov
2004-06-21 15:52 ` Reiner Steib
2004-06-21 17:35 ` Ted Zlatanov
2004-06-24 14:17 ` Kai Grossjohann
2004-06-24 14:43 ` Reiner Steib [this message]
2004-06-24 16:06 ` Ted Zlatanov
2004-06-25 6:23 ` Kai Grossjohann
2004-06-21 14:43 ` Ted Zlatanov
2004-06-18 21:20 ` Jonas Steverud
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=v9d63p819j.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--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).