From: Harry Putnam <reader@newsguy.com>
Subject: Agent download mark (@/%)
Date: 20 Jun 2001 11:10:24 -0700 [thread overview]
Message-ID: <m1lmmnyqs8.fsf@reader.newsguy.com> (raw)
A scenario happens here often enough to be a real pain, may be sloppy
usage on my part, but I haven't been able to identify what is really
the source of this.
In unplugged (agent) mode
Due to not fully grokked conditions of some sort, possibly having
marked as read while plugged or in some way overlooked, score filed,
or whatever, certain messages that did not get downloaded.
Later deciding to retrieve such messages, doesn't always work. Under
some condition, I think these messages are seen as being already
downloaded or expired or something. At any rate, they do not get
downloaded by marking %. Even if marked as unread.
I want gnus to downloaded % marked articles, regardless of any other
consideration except being expired from the server. That is, marking
with % should override any record gnus has of that message, and get it
downloaded. Even if it is a duplicate, then overwrite the old one.
How can I manage this?
reply other threads:[~2001-06-20 18:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m1lmmnyqs8.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).