From: Harry Putnam <reader@newsguy.com>
Subject: Agent Download technique for unusual groups
Date: Mon, 22 Oct 2001 13:31:40 -0700 [thread overview]
Message-ID: <m1itd7o1qr.fsf@reader.newsguy.com> (raw)
I'd like to hear about ways to do this proceedure.
Using gnus-agent for most of my reading:
I have a few groups that I read only casually and my casual reading
does not lend itself to category based on score file. Like scoring a
subject, author etc. to cause those to be downloaded.
What I'm trying currently is to set the category default to false and
list that group in that category. That way I get the author and
subject in summary buffer and mark with %, presss `J u'
(`gnus-agent-fetch-groups') to download them then M-g to actually get
them into the summary buffer in downloaded form.
This works but leaves a lot to be desired. For example: I'd like to
mark an article with something that would cause the agent to download
any messages to that thread. A thread watch mark like some other
newsreaders have. Yet still the category remain default false.
That is, I want a mark that causes a specific thread to be downloaded
as it comes in with no more effort than my initially marking a
specific message with %. I don't want to have to mark each newly
arrived (no body) message as it comes in.
I can think of at least one possibliity to do this using thread based
hand scoring, but can that work with a default of false? Are there
already existing ways to do this?
A better approach might be to just download the entire
group. (Category true) and be able to set gnus-agent-expire
differently for individual groups. Instead of the current setup where
gnus-agent-expire settings are unilateral. Combining that with the
ability to say what gnus-agent-expire actually expires. Like messages
with no bodys only or similar.
In short, G p mail setting be applied to nntp/agent groups.
next reply other threads:[~2001-10-22 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 20:31 Harry Putnam [this message]
2001-10-22 21:18 ` Kai Großjohann
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=m1itd7o1qr.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
/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).