From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Need suggestions for changing agent's downloadable mark.
Date: Sun, 18 Jan 2004 21:41:29 -0600 [thread overview]
Message-ID: <uektwip06.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <87llo52ksi.fsf@emptyhost.emptydomain.de>
Kai Grossjohann <kai@emptydomain.de> writes:
> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> I could fix this by editing the newsrc file but I'm concerned that any
>> number of people may have the same unrecognized problem. What I need
>> is a process, either manual or automatic, that cleans up the
>> downloadable marks.
>
> Doesn't the agent already have a feature where it does things with
> articles that aren't on the server anymore? Maybe it deletes NOV
> lines for those articles? It could also remove the downloadable mark
> for them.
I believe that you're thinking of gnus-agent-expire. It's a
possibility. I was hoping for something more automatic.
> While it is possible to download read articles, and users *might* wish
> to do that, we can be pretty sure that articles that aren't on the
> server any more are really not downloadable anymore ;-)
Well, I wasn't planning to forbid marking read articles. Especially
as the agent has a flag for marked newly fetched articles as unread
(that does seem to imply that some people fetch read articles). What
I was thinking of was a good deal more subtle. That is, you could
mark a read article in the current gnus session and fetch it, but you
could not mark that read article in this gnus session and then fetch
it in a future gnus session. Hmmm... That's probably sufficiently
subtle that people encountering it would call it a bug.
Kevin
prev parent reply other threads:[~2004-01-19 3:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 5:36 Kevin Greiner
2004-01-18 17:13 ` Simon Josefsson
2004-01-19 3:33 ` Kevin Greiner
2004-01-19 6:15 ` Simon Josefsson
2004-01-19 12:50 ` Kevin Greiner
2004-01-19 14:49 ` Simon Josefsson
2004-01-20 1:58 ` Kevin Greiner
2004-01-20 11:38 ` Simon Josefsson
2004-01-19 11:46 ` Harry Putnam
2004-01-18 18:06 ` Kai Grossjohann
2004-01-19 3:41 ` Kevin Greiner [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=uektwip06.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.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).