"John F. Morse" <jo...@example.invalid> writes:
>> alt.radio.networks.npr: 1-22516,22527,22530,22536-22537
>> I have .newsrc lines that are many times longer.
>I might ask, "why?" However it is your business whether or not to hoard.
Because if you hold an article as unread, .newsrc has to account for it;
.newsrc keeps track of read, not unread, articles.
>> Eventually, nn balks and does not acknowledge that I have read articles there.
>What do you mean by "balks"? Isn't a "balk" a temporary stop, followed
>by a go?
balk:
1. To stop short and refuse to go on: The horse balked at the jump.
2. To refuse obstinately or abruptly: She balked at the very idea of compromise.
Despite reading an newer article, nn can't/won't lengthen the
.newsrc to show that. Next time I start nn & go to that group, I
am shown it again as new.
>> My sledgehammer solution is to {for example} go to 22430 above &
>> edit the line to start 1-22430.
>Do you mean 22530? I don't find an article number listed that is less
>than 22516.
Yes, my error. In any case my intent should be clear; I am forced to mark
articles as read before I wish to do so.
>> Folks using trn/tin don't see to see this issue. As a long-time
>> user of nn {I tested betas for Kim Storm..} I can't imagine
>> changing.
>Don't "see" or don't "seem"?
"seem to see"
>> Suggestions?
>Catchup on the articles.
I wish to keep them marked as unread.
>Imagine changing to a different newsreader. You say TRN and TIN are
>reportedly without this problem (if you can really believe what unknown
>people say).
They are not unknown people; they are fellow customers of my ISP.
Some are good friends, others just casual ones I respect.
>Wait for someone to fix NN. Define "balks" so they will have a clue
>where to start.
See above. I surmised this was a place to find people interested in nn code.