[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Kibozing is defined by the OED as "grepping through
(parts of) the news feed". nnkiboze
is a back end that will
do this for you. Oh joy! Now you can grind any NNTP server
down to a halt with useless requests! Oh happiness!
To create a kibozed group, use the G k command in the group buffer.
The address field of the nnkiboze
method is, as with
nnvirtual
, a regexp to match groups to be "included" in the
nnkiboze
group. That's where most similarities between
nnkiboze
and nnvirtual
end.
In addition to this regexp detailing component groups, an
nnkiboze
group must have a score file to say what articles are
to be included in the group (see section 7. Scoring).
You must run M-x nnkiboze-generate-groups after creating the
nnkiboze
groups you want to have. This command will take time.
Lots of time. Oodles and oodles of time. Gnus has to fetch the
headers from all the articles in all the component groups and run them
through the scoring process to determine if there are any articles in
the groups that are to be part of the nnkiboze
groups.
Please limit the number of component groups by using restrictive regexps. Otherwise your sysadmin may become annoyed with you, and the NNTP site may throw you off and never let you back in again. Stranger things have happened.
nnkiboze
component groups do not have to be alive--they can be dead,
and they can be foreign. No restrictions.
The generation of an nnkiboze
group means writing two files in
nnkiboze-directory
, which is `~/News/kiboze/' by default.
One contains the NOV header lines for all the articles in
the group, and the other is an additional `.newsrc' file to store
information on what groups have been searched through to find
component articles.
Articles marked as read in the nnkiboze
group will have
their NOV lines removed from the NOV file.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |