Re: The agent shows ghost messages (was: spam-stat broken?)

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

Niklas Morberg <niklas.morberg@axis.com> writes:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Wed, 12 Feb 2003, niklas.morberg@axis.com wrote:
>>> 
>>> The move routines seem to be working better now, but after
>>> some more testing I still see the problem with non-existing
>>> messages being displayed in the summary buffer by the agent.
>>
>> Can you check now? If there is still a problem, something
>> is wrong in the interaction between the agent and
>> gnus-summary-move-article.
>
> There is a problem, but it has nothing to do with the spam
> functionality. I'm pretty sure the problem is with the agent.

Well, I don't use the spam functionality so this is going to be interesting.

> Here's a way to repeat it:
>
> 1. Start with two unread and undownloaded messages in a
>    group.
>
> 2. Read the first message.
>

Niklas, pls do the following command at this point:
M-: (debug-on-entry 'gnus-agent-expire)
M-: (setq gnus-verbose 7)

> 3. Move the second message to another group with `B m'
>    without reading it.

You should have been thrown into the debugger.  Did that happen?  Was
the first argument to gnus-agent-expire a list of one integer; the
article # of the article being moved?

Type 'c' to continue.

Take a look at the message buffer.  gnus-agent-expire should have
printed messages telling you that it removed the NOV entry for the
article in question.  Did it?

> 4. Exit the group.
>
> 5. Re-enter the same group. The second message shows up in
>    the summary buffer, but it not possible to look at it.
>    It has not been downloaded and it is not on the server.
>
> This only happens if gnus-agent-mark-unread-after-downloaded
> is nil. Setting g-a-m-u-a-d to non-nil makes the problem go
> away.

You should be using revision 6.142, or later, of gnus-agent.el.  Are
you?


Kevin