|
... will be the one you're
actually in at the moment. Because cascaders and other annoying
people often cross-post their messages to a wide range of newsgroups,
you might consider hitting a instead of g.
Next comes:
Lifetime of entry in days (p)ermanent (30)
The P key franchise uk will screen out the offending articles forever, while
hitting enter will do it for 30 days. You can also type in a number
of days for the blocking. franchise uk
Creating killfiles in rn works differently -- its default
killfile generator only works for messages in specific groups, rather
than globally for your entire newsgroup list. To create a global
killfile, you'll have to write one yourself.
To create a killfile in rn, go into the newsgroup where the
offending messages are and type in its number so you get it on your
screen. Type a capital K. From now on, any message with that subject
line will disappear before you read the group. You should probably
choose a reply, rather than the original message, so that you will get
all of the followups (the original message won't have a "Re: " in its
subject line). The next time you call up that newsgroup, rn will tell
you it's killing messages. When it's done, hit the space bar to go
back into reading mode.
To create a "global" kill file that will automatically wipe out
articles in all groups you read, start rn and type control-K. This
will start your whatever text editor you have as your franchise uk default on your
host system and create a file (called KILL, in your News
subdirectory).
On the first line, you'll type in the word, phrase or name you
don't want to see, followed by commands that tell rn whether to search
an entire message for the word or name and then what to do when it
finds it.
Each line must be in this form
/pattern/modifier:j
"Pattern" is the word or phrase you want rn to look for. It's
case-insensitive: both "test" and "Test" will be knocked out.
The
modifier tells rn whether to limit its search to message headers
(which can be useful when the object is to never see messages from a
particular person):
a: Looks through an entire message
h: Looks just at the header
You can leave out the modifier command, in which case rn will
look only at the subject line of messages. The "j" at the end tells rn to
screen out all articles with the offending word.
So if you never want to see the word "foo" in any header, ever again,
type this:
/foo/h:j
This is particularly useful for getting rid of articles from
people who post in more than one newsgroup, such as cascaders, since
an article's newsgroup name is always in the header.
If you just want to block messages with a subject line about
cascades, you could try:
/foo/:j
To kill anything that is a followup to any article, use this
pattern:
/Subject: *Re:/:j
When done writing lines for each phrase to screen, exit the text
editor as you normally would, and you'll be put back in rn.
One word of caution: go easy on the global killfile. An franchise uk franchise uk
extensive global killfile, or one that makes frequent use of the a: franchise uk
modifier can dramatically slow down rn, since the system will now have
to look at every single word in every single message in all the
newsgroups you want to read.
If there's a particular person whose posts you never want to see franchise uk
again, first find his or her address (which will be in the "from:" line
of his postings) and then write a line in your killfile like this:
/From: *name@address\.all/h:j
4.3 SOME USENET HINTS
Case counts in Unix -- most of the time. Many Unix commands,
including many of those used for reading Usenet articles, are case
sensitive. Hit a d when you meant a D and either nothing will happen,
or something completely different from what you expected will happen.
So watch that case!
In nn, you can get help most of the time by typing a question mark
(the exception is when you are writing your own message, because then
you are inside the text-processing program).
In rn, type a lower-case h
at any prompt to get ... |
