Xref: utzoo news.software.b:1351 news.misc:1395 Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!decuac!rayssd!gmp From: gmp@rayssd.ray.com (Greg Paris /exaflop meatbop/) Newsgroups: news.software.b,news.misc Subject: Re: more ways to kill articles Message-ID: <2239@rayssd.ray.com> Date: 5 May 88 17:11:43 GMT References: <2182@rayssd.ray.com> <14720@oddjob.UChicago.EDU> <7531@mcdchg.UUCP> Sender: gmp@rayssd.ray.com (Gregory M. Paris @ Raytheon Company, Portsmouth RI) Reply-To: gmp@rayssd.RAY.COM (Greg Paris /exaflop meatbop/) Organization: RAYtheon Sub Sig Div Lines: 25 Summary: HIDELINES is not good enough In article <7531@mcdchg.UUCP> heiby@mcdchg.UUCP (Ron Heiby) writes: > Although this doesn't actually kill the article, it is possible to tell > rn to "hide" the normal inclusion lines. The HIDELINE variable can be > set to something like "^>" and any line beginning with a "greater-than" > symbol will be hidden when you view the article. You can even use "|" > to hide more than one pattern. The hidden lines can be viewed by restarting > the article with the 'v' command. This is a nice feature of rn, but it's not good enough. I don't have a problem with included text per se, so I don't want to hide all included text by default. (I do use HIDELINES to hide multiply-included text, though.) What I want to be able to do is automatically (and with as little overhead as possible) junk articles that contain predominately more included text than original text. The 50% rule is probably extreme, but articles that contain 75% or more included text are nearly always not worth reading (my opinion). Another possibility might be to have a HIDELINES-like variable that will come into play after N contiguous lines of included text. -- Greg Paris /exaflop meatbop/ {att,decuac,gatech,necntc,sun,uiucdcs}!rayssd!gmp