Re: New agent code

[David S Goldberg <david.goldberg6@verizon.net>]

>>>>> On Mon, 25 Nov 2002 21:32:54 +0100,
>>>>> kai.grossjohann@uni-duisburg.de (Kai Großjohann) said:

> David S Goldberg <david.goldberg6@verizon.net> writes:
>> Well doing that and setting deactivate-mark to nil eliminated the
>> errors associated with undefined variables and functions, it resulted
>> in another problem, the attached backtrace which I got when I tried to
>> enter an nnimap folder with unread messages in it.  I was able to
>> enter a folder that did not have any unread messages in it, however.

> Ah, the backtrace appears to come from the checking code.  Just hit
> `c'.

Sadly that didn't work.  I kept getting the same backtrace for each c
I hit.  On the plus side, after a cvs update this morning, I no longer
have the back trace problem, but my inbox folder is messed up.  The
group buffer properly shows that there are new messages, but when I
enter the buffer, I can't see them unless I explicitly jump to them
(good thing I show article numbers in my summary line format).  It
doesn't happen in several other groups, so I figured something might
be wrong with the agent overview file.  I tried running
gnus-agent-regenerate and got this backtrace:

Signaling: (wrong-type-argument number-char-or-marker-p nil)
  gnus-agent-regenerate-group("nnimap+linus:INBOX.in-box" nil)
  gnus-agent-regenerate(nil)
  call-interactively(gnus-agent-regenerate)
  command-execute(gnus-agent-regenerate t)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net