Xref: utzoo comp.sources.d:1746 news.software.b:1086
Path: utzoo!mnetor!uunet!husc6!rutgers!rochester!udel!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!silver!creps
From: creps@silver.bacs.indiana.edu (Steve Creps)
Newsgroups: comp.sources.d,news.software.b
Subject: Re: rn kill file status display efficiency
Message-ID: <683@silver.bacs.indiana.edu>
Date: 28 Jan 88 17:02:35 GMT
References: <5365@tut.cis.ohio-state.edu> <1117@hao.ucar.edu>
Reply-To: creps@silver.UUCP (Steve Creps)
Organization: Indiana University Computer Science Department
Lines: 23

In article <1117@hao.ucar.edu> woods@hao.UUCP (Greg Woods) writes:
>In article <5365@tut.cis.ohio-state.edu> bob@tut.cis.ohio-state.edu (Bob Sutterfield) writes:
>>How can I encourage rn to count how many articles have been killed so
>>far, and if that matches the number of unread articles it saw when I
>>started that newsgroup, I should go on to the next group without
>>bothering to check all the rest of the kill file?

>   My observation of how rn works is that the first line in the KILL file
>takes a while to process, while all the subject lines of unread articles
>are read in. However, checking each additional line is a relatively fast
>process since all the article files do not have to be reopened to do this.
>I think you are worrying about something that is a relatively minor slowdown.

   It may be a minor slowdown if you're only interested in CPU time, but
when you take into consideration having to read it at 1200 baud it isn't
so minor. I personally would like to see an option to let you turn off
the display of junked articles. (It would reduce the time I spend in
rec.arts.startrek by at least 95% :-) )

-	-	-	-	-	-	-	-	-
Steve Creps on the VAX 8650 running Ultrix 2.0-1 at Indiana University.
creps@silver.bacs.indiana.edu, ...iuvax!silver!creps, creps@iubacs.bitnet
"F-14 Tomcat! There IS no substitute."