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

>>>>> "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).  The
   TZ> registry won't be a Gnus feature formally until after the current
   TZ> release is out of beta, that's why it's not in the manual.

I should do (gnus-registry-initialize) right after I 'require' it, correct?

   TZ> Before you do that, can you send me a trace of the problem?  Do M-x
   TZ> toggle-debug-on-error and you'll get a trace.

I tried this but it doesn't want to crash anymore.  Yes, I tried it before I
added (gnus-registry-initialize).  If I see any more errors I'll post a
backtrace.

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?  Why doesn't that cause alot of unacceptable overhead?

   >> My nnimap-split-fancy starts like this:
   >> 
   >> (setq nnimap-split-fancy
   >> '(|
   >> (: gnus-registry-split-fancy-with-parent)
   >> (: spam-split 'spam-use-regex-headers)
   >> ))
   >> 
   >> Is there something else I should have done?

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

How would one do that?

   >> Do I understand correctly that will scan my mailbox and immediately
   >> file this message together with its parent?  If so, it makes sense
   >> to do this as one of the first checks, correct?

   TZ> Usually, yes, this will group threads together.  It doesn't work with
   TZ> some MUAs that don't preserve the References header, though.

But nothiung bad would happen, right?  It would just not be split where I
might have wanted it go, right?

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?

-- 
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



  reply	other threads:[~2003-10-29 20:25 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   ` Jake Colman [this message]
2003-10-30 15:11     ` gnus-registry-split-fancy-with-parent Ted Zlatanov
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=76ptgfvljh.fsf@newjersey.ppllc.com \
    --to=colman@ppllc.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).