From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Agent downloading even when there isn't any new articles
Date: Sat, 14 Dec 2002 14:00:44 +0100 [thread overview]
Message-ID: <84adj8kb5v.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <upts5m9ul.fsf@xpediantsolutions.com>
kgreiner@xpediantsolutions.com writes:
> So, here's a question for the group, should gnus-agent-fetch-session
> mark articles that it fails to fetch as read? If so, what mark should
> I use? ancient,killed,del,expirable
Sometimes, Gnus shows yellow fg on black bg and, I think, a G (instead
of R/Y/K/...) for canceled articles. That appears to be the right
mark. But I don't know which mark it is.
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-12-14 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 13:20 Henrik Enberg
2002-12-14 5:46 ` kgreiner
2002-12-14 11:32 ` Henrik Enberg
[not found] ` <uhedesiom.fsf@xpediantsolutions.com>
2002-12-28 17:53 ` Lars Magne Ingebrigtsen
2002-12-28 17:53 ` Lars Magne Ingebrigtsen
2003-01-06 7:31 ` kgreiner
2002-12-14 13:00 ` Kai Großjohann [this message]
2002-12-28 17:51 ` Lars Magne Ingebrigtsen
2002-12-28 17:51 ` Lars Magne Ingebrigtsen
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=84adj8kb5v.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).