Re: gnus-registry-split-fancy-with-parent

[Jake Colman <colman@ppllc.com>]

(gnus-registry-initialize) is not part of the Gnus 5.10.2 package in
XEmacs. Since I am going to want your support, I decided to bite the bullet
and went with the latest cvs gnus.  This way, things like (spam-initialize)
and (gnus-registry-initialize) all work as you say.

Does (gnus-registry-initialize) have to be executed before (spam-initialize)
or is there no interdependency?  BTW is it required that I "(setq
spam-use-bogofilter t)" before doing (spam-initialize)?

Using gnus-registry-split-fancy-with-parent I am seeing messages "traced
... to group nil".  Why is it never finding a group to put it in?  I'm
assuming that this test, when it works, will split faster than forcing the
email through all my 'any' splits.  Is this correct?

>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:

   TZ> On Wed, 29 Oct 2003, colman@ppllc.com wrote:
   >>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
   >> 
   TZ> On Wed, 29 Oct 2003, colman@ppllc.com wrote:
   >> >> I tried using this and gnus crashed out.  What is the correct
   >> >> way use this function?
   >> >> 
   >> >> gnus-registry is apparently not loaded by default so I
   >> >> 'require' it early on in my .gnus file (right after I (require
   >> >> 'spam).
   >> 
   TZ> That's not enough, you need to do (gnus-registry-initialize).
   TZ> The registry won't be a Gnus feature formally until after the
   TZ> current release is out of beta, that's why it's not in the
   TZ> manual.
   >> 
   >> I should do (gnus-registry-initialize) right after I 'require' it,
   >> correct?

   TZ> I'm pretty sure you don't need to 'require' anything because of the
   TZ> magic of autoloading, and it works that way for me.

   >> When the registry is initilalized, it tracks where all articles have
   >> been filed?  And that's what allows
   >> (gnus-registry-split-fancy-with-parent) to know what to do?  

   TZ> Yes.

   >> Why doesn't that cause alot of unacceptable overhead?

   TZ> Well, you can look at the source if you are interested in that level
   TZ> of detail.  Basically we keep a fast index of the article IDs and the
   TZ> groups they are in.

   TZ> No, this is fine.  You may also want tracking by subject, but
   TZ> that's optional and experimental.
   >> 
   >> How would one do that?

   TZ> Do M-x customize-group gnus-registry and you'll see that option and
   TZ> some others.  Subject tracking is in CVS only, I think.

   TZ> Usually, yes, this will group threads together.  It doesn't
   TZ> work with some MUAs that don't preserve the References
   TZ> header, though.
   >> 
   >> But nothiung bad would happen, right?  It would just not be split
   >> where I might have wanted it go, right?

   TZ> Right, it will go to the next splitting rule.

   >> I think the latest gnus package (as available through XEmacs) is
   >> 5.10.2.  Will the registry be part of 5.10.3?  Will there be a
   >> 5.10.3?

   TZ> I'm not sure about the exact release plans.  In the worst case, you
   TZ> can always get just gnus-registry.el from CVS - it doesn't depend on
   TZ> anything and nothing depends on it.  I think it will be a part of
   TZ> Gnus, though.

   TZ> Ted

-- 
Jake Colman                     

Principia Partners LLC                    Phone: (201) 209-2467
Harborside Financial Center                 Fax: (201) 946-0320
902 Plaza Two                          E-mail: colman@ppllc.com
Jersey City, NJ 07311                 www.principiapartners.com