#7 too long to get overview info

[Eric B. Hymowitz]

Greetings.

I don't know if any active development is going on, but I use trn regularly and love it.

I've run into a problem. My NNTP provider keeps a very very very very long history of articles.

So when I open a newsgroup, trn issues the LISTGROUP command which results in a list of article numbers from (in this case) 1 to over 1,250,000. This takes a long time.

Then, in the background, it runs the XOVER command and downloads more detailed information. It does this again in numerical order from 1 to 1,250,000 ... but the articles I am most interested in are most likely to be the highest numbered articles.

I don't know the NNTP protocol very well, but it looks like the LISTGROUP command in the nntp_artnums() function can be replaced by the GROUP command with no ill effects.

Once I'm in the article selector, I was hoping that the XOVER calls(s) can be rewritten to process the articles in reverse order (I know that the NNTP protocol won't do them in complete reverse order, but maybe it can start with the higest-numbered 100 articles, and then go back in groups of 100?)

Thanks.

--hymie!

[Eric B. Hymowitz]

When I said

I don't know the NNTP protocol very well, but it looks like the LISTGROUP command in the nntp_artnums() function can be replaced by the GROUP command with no ill effects.

I was mistaken. The first new message in the first group I read gets incorrectly marked as read. I can't figure out why, but I'm not a programmer. :(