Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: gnus-registry-split-fancy-with-parent
Date: Thu, 30 Oct 2003 10:11:17 -0500	[thread overview]
Message-ID: <4nk76mwyju.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <76ptgfvljh.fsf@newjersey.ppllc.com> (Jake Colman's message of "Wed, 29 Oct 2003 15:25:22 -0500")

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?

I'm pretty sure you don't need to 'require' anything because of the
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?  

Yes.

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

Well, you can look at the source if you are interested in that level
of detail.  Basically we keep a fast index of the article IDs and the
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?

Do M-x customize-group gnus-registry and you'll see that option and
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?

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?

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

Ted



  reply	other threads:[~2003-10-30 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 19:54 gnus-registry-split-fancy-with-parent Jake Colman
2003-10-29 20:09 ` gnus-registry-split-fancy-with-parent Ted Zlatanov
2003-10-29 20:25   ` gnus-registry-split-fancy-with-parent Jake Colman
2003-10-30 15:11     ` Ted Zlatanov [this message]
2003-10-30 15:31       ` gnus-registry-split-fancy-with-parent Jake Colman
2003-10-30 16:01         ` gnus-registry-split-fancy-with-parent Ted Zlatanov
2003-10-30 16:53           ` gnus-registry-split-fancy-with-parent Jake Colman
2003-10-31 16:27             ` gnus-registry-split-fancy-with-parent 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=4nk76mwyju.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).