Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Too long .newsrc

12 views
Skip to first unread message

David Lesher

unread,
Aug 10, 2012, 7:05:04 PM8/10/12
to
Panix has a news server with very long expiration times. But nn seems
to have an issue with that.

If you read-up the group, no problem. But if you keep
unread articles, it gets longer. For example:

alt.radio.networks.npr: 1-22516,22527,22530,22536-22537

I have .newsrc lines that are many times longer. Eventually,
nn balks and does not acknowledge that I have read articles there.

My sledgehammer solution is to {for example} go to 22430 above &
edit the line to start 1-22430.

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.

Suggestions?
--
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433

John F. Morse

unread,
Aug 10, 2012, 7:22:30 PM8/10/12
to
David Lesher wrote:
> Panix has a news server with very long expiration times. But nn seems
> to have an issue with that.
>
> If you read-up the group, no problem. But if you keep
> unread articles, it gets longer. For example:
>
> 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.


> 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?


> 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.


> 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"?


> Suggestions?
>


Think about your question so people will know what you really mean.

Catchup on the articles.

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).

Wait for someone to fix NN. Define "balks" so they will have a clue
where to start.

HTH.

73.

--
John

When a person has -- whether they knew it or not -- already
rejected the Truth, by what means do they discern a lie?

David Lesher

unread,
Aug 10, 2012, 11:19:01 PM8/10/12
to
"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.

Aaron W. Hsu

unread,
Aug 27, 2012, 2:07:42 PM8/27/12
to
David Lesher <wb8...@panix.com> writes:

>Panix has a news server with very long expiration times. But nn seems
>to have an issue with that.

I have added this on my list of things to examine in the next release
of NN. This may take a while to get to, but hopefully I will have a
diagnosis of it some time and see if I can fix the problem you are
experiencing.

https://github.com/arcfide/Unicode-NN/issues/6

--
Aaron W. Hsu | arc...@sacrideo.us | http://www.sacrideo.us
Programming is just another word for the lost art of thinking.

David Lesher

unread,
Aug 28, 2012, 5:18:45 PM8/28/12
to
Aaron W. Hsu <arc...@sacrideo.us> writes:


>>Panix has a news server with very long expiration times. But nn seems
>>to have an issue with that.

>I have added this on my list of things to examine in the next release
>of NN. This may take a while to get to, but hopefully I will have a
>diagnosis of it some time and see if I can fix the problem you are
>experiencing.

> https://github.com/arcfide/Unicode-NN/issues/6

Thanks!
0 new messages