From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Need suggestions for changing agent's downloadable mark.
Date: Sun, 18 Jan 2004 18:13:28 +0100 [thread overview]
Message-ID: <ilur7xxuqmf.fsf@latte.josefsson.org> (raw)
In-Reply-To: <ud69hrf6o.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Sat, 17 Jan 2004 23:36:31 -0600")
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> I've noticed a problem with the agent's downloadable mark. As gnus
> currently works, a downloadable mark will persist until either a) the
> user manually removes it, or b) the agent successfully downloads the
> marked article.
>
> What I've found, by reading my own newsrc file, is that I have a
> number of ancient downloadable marks stored in it. Apparently, I
> marked a number of articles as downloadable then changed my mind and
> ran catchup on the group. Now, the server's active range has moved so
> I can't get these articles back in the summary buffer to manually
> remove the mark.
>
> 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.
>
> Right now, my best idea is to change downloadable marks to say that
> downloadable marks on READ articles will not be stored in the newsrc
> file. This is actually a very simple change to implement and, I
> suspect, that it will have minimal impact on users.
>
> Would anyone object to this change? Better yet, does anyone wish to
> propose an alternative solution?
How about removing downloadable marks on articles that are no longer
within the active range? IIRC, this is what happens with tick marks
etc on out-of-bounds article numbers. I'm a bit surprised it doesn't
happen automatically for downloadable marks. Or perhaps that
behaviour is buggy for all marks now, I'm not sure I would notice if
the flags weren't removed.
next prev parent reply other threads:[~2004-01-18 17:13 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 [this message]
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
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=ilur7xxuqmf.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).