[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gnus-registry problems

From: Ted Zlatanov
Subject: Re: Gnus-registry problems
Date: Tue, 29 Jun 2004 13:17:09 -0400
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux)

On Tue, 29 Jun 2004, address@hidden wrote:

> 1. One test: I receive a message and move it to
> Followups with proper References headers will be
> split to, too. This is olly good.

Set the gnus-verbose to 10 and see what the Messages buffer says.

> 2. Another test: I write a message with Gcc:
> and send it off. Followups to that message are not split to that
> group (unless I make some specific splitting rule). Is it supposed
> to work like this?

Depends.  I don't know if Gcc will write the article with the correct
message ID (but common sense says it should).  Again, see what the
Messages buffer says.  Maybe there's a place where I'm not calling
the right hook.

> 3. A third test: I write a followup to the message of item 1, but I
> put in empty References headers, to simulate people who write to me
> using broken software. This followup is not split to
> Why? Shouldn't the (setq
> gnus-registry-track-extra (quote (subject))) take care of this? The
> subject was "Plommegr√łt", so it should be long enough for
> gnus-registry to have something to split on, right?

The registry keeps a lookup table of subjects related to message
IDs.  You need to check if that subject is in the registry at all
(grep your registry file, for instance) and then do 
t M-: (gnus-registry-split-fancy-with-parent) in the buffer of the
article (`t' will show the whole article).  With gnus-verbose set to
10, I need to know what the Messages buffer says.

There are some reasons why the subject lookup will fail, chiefly that
the same subject may be in various groups (but there are others, see
the function gnus-registry-split-fancy-with-parent).  If there's more
than one match for a subject, the lookup is considered a failure.  I
thought about this, and it seems to be the best way to handle multiple
groups.  I'm open to suggestions if you think otherwise.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]