Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2258 comp.os.linux.misc:12576
Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!agate!ames!pacbell.com!amdahl!amdahl.uts.amdahl.com!agc
From: agc@uts.amdahl.com (Alistair G. Crooks)
Subject: Re: Impressions: FreeBSD vs Linux
Message-ID: <1994Apr12.104202.23291@uts.amdahl.com>
Organization: Amdahl Corporation, Sunnyvale CA
References: <R8m2Jc1w165w@oasys.pc.my> <2nv1ls$531@harbinger.cc.monash.edu.au> <2od4oh$9c7@menudo.uh.edu>
Date: Tue, 12 Apr 1994 10:42:02 GMT
Lines: 215
In article <2od4oh$9c7@menudo.uh.edu> cosc19v2@menudo.uh.edu (cosc19v2) writes:
[a complete load of misinformed crap...]
OK. I've seen enough of this trash go by now, and have got so annoyed
with the bickering from both sides that, after my signature below,
people will find the rn killfile FAQ. Not much help for people who
don't use rn, but it makes me feel a lot better...
Welcome to my kill file, cosc19v2. Give my regards to Mrs cosc19v2, and
all the little cosc19v2-ettes.
Alistair
--
Alistair G. Crooks (agc@uts.amdahl.com) +44 252 346377
Amdahl European HQ, Dogmersfield Park, Hartley Wintney, Hants RG27 8TE, UK.
From: phillips@syrinx.umd.edu (Leanne Phillips)
Newsgroups: news.newusers.questions,news.software.readers,news.answers
Subject: rn KILL file FAQ
Message-ID: <killfile.faq_732728203@syrinx.umd.edu>
Date: 21 Mar 93 15:36:46 GMT
Expires: 21 Apr 93 03:36:43 GMT
Reply-To: phillips@syrinx.umd.edu
Followup-To: news.newusers.questions
Organization: University of Maryland, College Park
Lines: 183
Approved: news-answers-request@mit.edu
Supersedes: <killfile.faq_730133243@syrinx.umd.edu>
NNTP-Posting-Host: syrinx.umd.edu
Originator: phillips@syrinx.umd.edu
Archive-name: killfile-faq
Last modified: 23 Oct 1992
Send comments, suggestions, corrections to phillips@syrinx.umd.edu.
Rn and trn, and other varieties of rn, have a very useful feature called
the KILL file, which allows you to kill (skip over) articles that you don't
want to see. There is some support for killfiles in xrn, but the support is
limited; nothing in here is guaranteed to work for xrn. See the xrn
man page.
KILL files come in two forms:
Global: In your News directory, you will have the file KILL.
Local: In your News directory, the killfile for group foo.bar
will be foo/bar/KILL.
The difference between the two is that there can be one killfile for
each group (the local killfile), and that killfile affects only the
particular newsgroup (foo/bar/KILL affects only foo.bar; baz/quex/KILL
affects only baz.quex, etc). The global killfile affects all newsgroups.
(There's a way to change the default names of the killfiles, but it's
more complicated than I want to get into here. See the rn(1) man page.)
Killfiles allow you to kill articles based on a number of criteria:
a subject line, a general subject, articles from one poster, articles
from one site, articles cross-posted from any other group, or from one
other group in particular, and articles that are follow-ups to anything at
all (that is, anything with the Re: in the subject line). You can also
kill articles with a particular string anywhere in the article.
This article assumes you know how to use an editor and that you have
created the directories for any local killfiles you may need. Remember
that the name of the file is KILL, not kill or Kill; caps are important.
The general style for building a kill line is:
/pattern/modifiers:command
Now, that is obviously not useful to know without understanding it. The
modifiers and commands are all explained in the rn man page, but here are
some useful ones:
Modifiers:
a: all, look through the entire article for the pattern
h: look through the header of the article for the pattern
Commands:
m mark as unread
j mark as read
= show subject line
If no modifier appears before the colon, only the subject line of the
article is searched. More than one command can be performed by using
the style:
/pattern/modifier:command:command
Thus, for instance, you can use j and = together to see the exact subject
lines being killed.
It doesn't matter if you use uppercase or lowercase in the pattern; the
program will assume they're the same thing. That is, "Test" and "test"
used in the pattern mean exactly the same thing; only one is necessary.
If you want case to matter, see the rn(1) man page, the 'c' modifier.
The easiest way to kill a subject line is to kill it from within the
newsgroup. When the subject line comes up that you want to kill, instead
of using 'n' to skip that article or 'k' to kill the subject for that
session, type 'K'. The subject line will then be entered into your KILL
file for that group. If you want to put that line into your global KILL
file, you'll have to do that yourself. (If you don't need it in your global
file, it's best not to put it there - global kill files slow down your news
reading a lot. So does using the 'a' modifier; use it sparingly.)
(I should mention here the easiest way to start editing your kill files.
Typing control-k when you're being asked to pick a newsgroup to read will
start you editing the global killfile; typing the same thing when you're
reading a newsgroup will start up the editing with the kill file for that
group. If it doesn't exist, it will create it - including the directories
necessary. This method is particularly recommended for people creating their
first kill file.)
To kill a general subject, ie any 'test' messages, put in the pattern:
/test/:j
This will kill anything with the word 'test' in the subject line.
To kill anything that is a followup to any article, use this pattern:
/.*Re:/:j
This kills anything beginning with Re:.
To kill cross-posts from one particular group, say foo.bar, try this:
/Newsgroups:.*[ ,]foo\.bar/h:j
This searches the header (the 'h' modifier) for any line containing the
string 'Newsgroups:' (which all articles do), as well as the string
'foo.bar'. The other elements of this line are part of the regular
expression meta-language; see the ed(1) man page for more details.
(Note that all of them are necessary, particularly the '\' before the
'.' in foo\.bar.)
To kill all cross-posts, from any group at all:
/Newsgroups:.*,/h:j
If the Newsgroups: line has a ',' in it, it's a cross-post, and therefore
this will find it.
Note that the above line searches the entire header, included the
Subject: line, for that pattern. So a Subject line like:
Subject: I hate the Newsgroups: line, don't you?
would get killed by that pattern, because it has a 'Newsgroups:' part, and
a ','. To make it work properly, use the 'start of line' character, ^.
The ^ isn't actually there when you look at the header yourself; it just
means to look for the beginning of the line. So, to kill cross-posts:
/^Newsgroups:.*,/h:j
should be used instead. (Use of the ^ is recommended if you know the
pattern you want to catch will be at the beginning of the line; it makes
searching a lot faster.)
To kill articles from a single poster, you need to know the userid and
nodename of the poster; for this example we'll use noone@anywhere.all.
/From: *noone@anywhere\.all/h:j
For articles from a particular site, just remove the 'noone' from the
previous line, and articles from the machine 'anywhere.all' will be killed.
(Note again that the \ is important.)
Now, after all that, you might suddenly find out that you killed articles
from someone whose posts you want to read even if they write about subjects
you don't want to read. For that, you need to 'unkill' the articles by
them:
/From: *name of person you want to read/h:m
So, if you suddenly decided you wanted to read noone@anywhere.all's
postings, after having deleted them above, you would add this line:
/From: *noone@anywhere\.all/h:m
The 'm' becomes useful suddenly. You can substitute m for j any time
you need to, up above. In fact, you can kill everything in a newsgroup and
only read what you want to read by using the 'm' feature, and putting this
line at the top of your KILL file:
/^/:j
This method has a problem, though. Specifically, it marks even those
you've already read (really read, not just marked as read) as unread. So,
there's another way to do it:
/pattern/:=:M
(check the rn(1) man page for the M command). This lists all the subjects
of the new articles, and then gives those articles to the M command. (You
then have to type 'Y' after the M command has finished.) (For more complete
information, please write me, and I'll forward on to you an example that was
posted by David Tamkin.)
Finally, you can kill (or mark, of course) a particular pattern appearing
anywhere in the article, as opposed to just the Subject: line or the header:
/pattern/a:j
and
/pattern/a:m
This is useful for, for instance, killing all articles by a certain user,
followups to said user's articles, and even mention of the user by userid
and node, or, conversely, by marking all of those conversations as unread
so you can read them if they've been killed accidentally by your other
entries.
Further information is available in the rn man page, particularly on
other available commands and modifiers. Regular expression syntax is
in the ed(1) man page; the xrn man page gives information about the quirks
of xrn in relation to killfiles.
I'd like to thank Jonathan Kamens and Rich Salz in particular for their
help, and everyone else who's sent in comments, criticisms, and suggestions;
keep them coming, folks!
Minor administrative note to the suggestors: Several people have suggested
that, in junking all of the articles and then marking only the desirable
ones to read, you need to use the 'r' modifier (search read articles as
well as unread). According to the man page I read, you don't need that;
if 'm' is the first command, the 'r' is assumed. If anyone wants to test
this and tell me it's wrong, please do. But please only tell me if it's
wrong; I'll assume it's right until someone tells me otherwise. :-)
Leanne Phillips
"Go not unto the Elves for counsel, for they will say both yea and nay."
"Now is _not_ a good time, Keiko!" - Worf, "Disaster"
"Variety is the spice of life, and I don't want to die." - Scott Borst