agent-fetching messing with the "first" unread article

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

Running a CVS update from Mon Jan  6 10:35:29 2003 EST

Ever since the summary line update code was added to
gnus-agent-fetch-selected-article, which I added to
gnus-select-article-hook like so:

(add-hook 'gnus-select-article-hook
	  (lambda ()
	    (if (eq (car (gnus-find-method-for-group
			  gnus-newsgroup-name))
		    'nnimap)
		(gnus-agent-fetch-selected-article))))

I find that gnus-summary-first-unread-article no longer works as I
expect.  I enter a group and see a nice threaded display with the
threads sorted more or less by date.  I press `.' and get to the first
new article in the first thread shown in the display (I fetch earlier
articles so some old ones are showing too).  I get a message about the
article being fetched and the summary line is updated to indicate the
article is now in the agent.  In the summary, there is another unread
article immediately below the one I am now reading.  I press `.' again
expecting to go to that article.  Instead I am jumped to an article in
a completely different thread.  Removing the above hook fixes the
problem for me.

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