From: Rade Markovic <markovicr@softhome.net>
Subject: Re: Agent aggravation
Date: 07 May 2000 13:38:05 +0200 [thread overview]
Message-ID: <87vh0q4mle.fsf@debilan.linux.hr> (raw)
In-Reply-To: Harry Putnam's message of "05 May 2000 05:06:39 -0700"
Harry Putnam <reader@newsguy.com> writes:
> Once the agent has bypassed downloading a message, due to it not
> satisfying the predicate. (in this case "high")
>
> Then the user decides they want to download one of those bypassed
> messages, there seems to be no way to do this handily.
>
> Finding the message when "plugged" and marking it as unread and with
> the "%" agent download mark seems like it should do the trick but does'nt.
I don't understand why you should go plugged. You still possess
headers of those bypassed articles unless you expunged them by your
score files. In that case, try putting something like
(mark -1000)
in your appropriate score file, and "low" articles down to -1000 will
be unread and visible, so you can operate on them (with @)
offline.
Or, simply remove expunge statement from your score file and operate
on read headers.
HTH
prev parent reply other threads:[~2000-05-07 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-05 12:06 Harry Putnam
2000-05-07 11:38 ` Rade Markovic [this message]
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=87vh0q4mle.fsf@debilan.linux.hr \
--to=markovicr@softhome.net \
/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).