From: jbw@cs.bu.edu (Joe Wells)
Subject: miscellaneous Gnus questions
Date: Tue, 18 Jun 1996 19:30:54 -0400 [thread overview]
Message-ID: <199606182330.TAA27541@csb.bu.edu> (raw)
Hi, folks,
Here are some miscellaneous Gnus questions:
1. What keys/command do I use to re-scan all groups from a particular
server? (For example, I want to rescan all of my nnml groups without
rescanning any nntp or nndir groups.) I know there are commands to (1)
re-scan all groups on a particular level and (2) re-scan a particular
group (does this ever affect other groups?), but that is not what I
want.
2. What is the difference between gnus-subscribe-alphabetically and
gnus-subscribe-hierarchically? I have read the documentation and
looked at the source code yet clarity eludes me.
3. How do I arrange for articles to be marked as expirable from a score
file without affecting the treatment of articles by ordinary reading?
4. How do I arrange for score-file changes to be specified by a score
file? What I want to do is completely wipe out all trace of the
existence of a particular person. So not only do I want to kill all of
his articles, but I want to kill any followups to his articles, to the
nth generation. The way I envision this happening is that a score file
entry would match the "from" field for this person and then add a new
SCORE file entry for the "message-id" field of the current article.
But the only action a score file entry that matches on the "from" field
can take is to raise or lower the score of the current article.
5. For mail groups, the "%R" format spec for gnus-group-line-format counts
all messages that have ever existed in the group, including those which
have been destroyed by the "B DEL" command. The information it uses
seems to come from the active file. Is there some way to get an
accurate count of the *existing* read messages from the "%R" format
spec?
6. In the summary buffer, what is difference between "M P b" and "M P a"?
They seem to do the same thing and the documentation strings (from "C-h
k") are not enlightening.
--
Joe Wells <jbw@cs.bu.edu>
next reply other threads:[~1996-06-18 23:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-18 23:30 Joe Wells [this message]
1996-06-19 6:21 ` Lars Magne Ingebrigtsen
1996-06-19 12:46 ` Jack Vinson
1996-06-19 13:12 ` Lars Magne Ingebrigtsen
1996-06-22 20:08 ` Joe Wells
1996-06-24 13:46 ` Colin Rafferty
1996-08-28 6:22 ` Lars Magne Ingebrigtsen
1996-08-28 22:26 ` Roger Williams
1996-08-29 0:54 ` Roger Williams
1996-06-25 21:48 ` Hallvard B Furuseth
1996-06-19 8:26 ` Per Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199606182330.TAA27541@csb.bu.edu \
--to=jbw@cs.bu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).