From: Harry Putnam <reader@newsguy.com>
Subject: agent % mark get over ridden somehow
Date: Tue, 27 Nov 2001 09:15:09 -0800 [thread overview]
Message-ID: <m1herg16g2.fsf@reader.newsguy.com> (raw)
This is an irritant I've run into often enough to cause this post.
It's not totally reproducable, at least I don't know how to reproduce
it on demand. However it continues to happen so apparently some set
of circumstance will provoke it.
Seems like it might be a case of gnus listening to the wrong
information source.
Circumstances I do know about:
While unplugged:
Mark a message that was not retrieved by download score rules with %.
In semi-recent and up Oort one can then (theoreticlally) while in the
same summary buffer, press `J j' to go plugged then `J u' to download
current group, and snag any messages with % marks. Then return to
unplugged with `J j'.
If I then try to access that message later when unplugged I get the
`G' symbol and am told it has either been expunged or is not
available. But wait, I just down loaded it a few moments ago.
Somehow gnus doesn't believe that. But a search of the directory
shows the message is in fact there. None the less, gnus obstinately
tells me it isn't. Even if I press `j' and feed it the article number
or message id. Seems like some record gnus is looking at is giving it
bad information.
reply other threads:[~2001-11-27 17:15 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=m1herg16g2.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).