On 2/3/01 11:02 PM, "Dan Crevier" <[EMAIL PROTECTED]> wrote:
Actually, it’s not a bug. It means that there are unread messages that are on the server, but you haven’t downloaded. You can click the toolbar button to download more. The account settings let you set how many messages will be downloaded when you connect.That's interesting. Very frequently I will click on a newsgroup — which is supposed to display all new messages on the server (as long as there aren't more new ones than my header number limit) — and then I'll rapidly click on each new unread heading to download and read the message, only to find that the newsgroup name is still bold in the folder pane, showing 2 or 3 unread messages. Are you saying that in the 30 seconds since I first clicked on the newsgroup and downloaded 3 or 4 headers, another 2 or 3 have since been uploaded there? That's possible, I guess, but it happens rather more frequently than feels right.
Selecting mark all as read marks the undownloaded messages as read as well, so it doesn’t show an unread count.
Dan
It also means that command-L, "Refresh Message List" should get these new headers, but it seems to me that I've tried it and it doesn't. I'll be more vigilant in future. Of course the toolbar button "More", like "Get More Messages" in the View menu, gets a lot more, because it gets older messages too. Some groups have thousands of messages on the server, many predating the first batch I downloaded, and – yes - unread. But if I have already Marked All those as Read, which are these new 2 or 3 suddenly showing as Unread? I don't want to download another 100 older headers just to get these 2 or 3. It still seems a bit mysterious to me.
I've been checking. Although occasionally command-L presents 1 or 2 brand new headers from the server that have just been uploaded there, 95% of the time nothing new arrives. When I click "More", I get the correct number of headers (2 or 3 usually) from about 2 months ago: December 9 and 10, 2000, appeared today. Since I have previously "Marked All as Read", those headers should not be showing as Unread and annoying me this way, should they? If this isn't a bug (albeit a different one than i first thought), what is it?
--
Paul Berkowitz
