Re: Gnus-registry problems

[Ted Zlatanov]

On Thu, 01 Jul 2004, stm+direct_reply@bacchus.pvv.org wrote:

> Ted wrote:
>> If you get more than one debug call, the article subject is in
>> multiple groups somehow.  If you get just one, there's a bug.
> 
> Here's the Backtrace (but I don't know how to use the debugger):
> 
> --8<---------------cut here---------------start------------->8---
> Debugger entered: ("Ibsens ripsbusker" "Ibsens ripsbusker" nil
>       "nnmaildir:mail.foo")
[...]

Hit 'c' to continue.  I need to know what happens the second time
this is triggered, if at all.

Generally you can hit 'c' for non-fatal debugger calls, and 'q' to
back out of a fatal call.

>>> Another thing: Might it be an idea that the
>>> gnus-registry-split-fancy-with-parent function consider the
>>> In-Reply-To header if there is no References ?
>>
>> We already do that in gnus-registry-split-fancy-with-parent:
>>
>> (message-fetch-field "in-reply-to")
>>
>> is it not working correctly?
> 
> I don't think so. In the e-mail we're discussing, I inserted an empty
> References header, and, unfortunately, it didn't get split according
> to the Subject. However, Gnus still inserted the In-Reply-To header,
> which didn't seem to be used. (Else I guess the e-mail would have been
> split correctly/as expected).

References is taken first, then iff it was not found In-Reply-To is
used.  So make sure you test with a message that has no References
header.

Should we make the registry take In-Reply-To if References exists but
is empty?  I don't know about In-Reply-To so I can't make that call.

Ted