Oort, agent - fetching read articles

Oort, agent - fetching read articles

[Paul Stodghill]

I've noticed that the agent in Oort gnus does not fetch all of the
articles that I expect it to, and it seems to be that the articles that
it doesn't fetch have been read before I try to fetch them.

The newsgroups in question are in a category whose predicate is "true".
I am not explicitly marking articles for downloading. I'm just doing a
"J s" in the *Group* buffer.

Is the agent supposed to fetch articles that have already been read? Is
not, there some way to get it to do so?

Thanks.

Re: Oort, agent - fetching read articles

[Simon Josefsson]

Paul Stodghill <stodghil@cs.cornell.edu> writes:

> I've noticed that the agent in Oort gnus does not fetch all of the
> articles that I expect it to, and it seems to be that the articles that
> it doesn't fetch have been read before I try to fetch them.
>
> The newsgroups in question are in a category whose predicate is "true".
> I am not explicitly marking articles for downloading. I'm just doing a
> "J s" in the *Group* buffer.
>
> Is the agent supposed to fetch articles that have already been read? Is
> not, there some way to get it to do so?

No, the behaviour is hard coded.  I think I posted a patch here a
while ago that introduced a new agent predicate `read'.  I'm not sure
if it still applies (or works) correctly, maybe you could try.

Re: Oort, agent - fetching read articles

[Harry Putnam]

Simon Josefsson <jas@extundo.com> writes:

> Paul Stodghill <stodghil@cs.cornell.edu> writes:
> 
> > I've noticed that the agent in Oort gnus does not fetch all of the
> > articles that I expect it to, and it seems to be that the articles that
> > it doesn't fetch have been read before I try to fetch them.
> >
> > The newsgroups in question are in a category whose predicate is "true".
> > I am not explicitly marking articles for downloading. I'm just doing a
> > "J s" in the *Group* buffer.
> >
> > Is the agent supposed to fetch articles that have already been read? Is
> > not, there some way to get it to do so?
> 
> No, the behaviour is hard coded.  I think I posted a patch here a
> while ago that introduced a new agent predicate `read'.  I'm not sure
> if it still applies (or works) correctly, maybe you could try.

Not being code literate, I haven't really tried to devine out what the
code really does, but it seems that marking such messages unread
should then have the desired affect, but that doesn't always work
either.  At the very least one would expect that using the explict %
mark should have the desired affect but that doesn't always work
either.

It would be nice if at least the % mark forced the agent to download a
message, regardless of read/unread or anything else, even overwriting
it if already on disk if need be.  Can that be managed?

Far as I can see, the only really sure fire way to get a message
downloaded if there is a question, is to go `plugged' and mark it for
cache, and then of course it isn't under the agents care.

Re: Oort, agent - fetching read articles

[Lars Magne Ingebrigtsen]

Harry Putnam <reader@newsguy.com> writes:

> At the very least one would expect that using the explict %
> mark should have the desired affect but that doesn't always work
> either.

In what instances does giving an article the "%" mark not lead to it
being downloaded?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Oort, agent - fetching read articles

[Harry Putnam]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > At the very least one would expect that using the explict %
> > mark should have the desired affect but that doesn't always work
> > either.
> 
> In what instances does giving an article the "%" mark not lead to it
> being downloaded?

That doggone pile of lisp won't even download a `%' marked article when
it is expunged from the server..... just kidding.

Trying just now, on some old near expunged messages that my predicate
didn't download, I get good ( the expected) results.  But there have
been occasions when this did not work.  I will try to report on one
when it next happens.  Assuming it wasn't something like my opening
joke at work.

Re: Oort, agent - fetching read articles

[Harry Putnam]

Harry Putnam <reader@newsguy.com> writes:

> Trying just now, on some old near expunged messages that my predicate
> didn't download, I get good ( the expected) results.  But there have

Doing the chore above reminded me to ask for a feature whereby group
buffer `J u' (agent fetch a single group)  is available in summary
buffer too.

This would allow user to mark %, go plugged, and J u.  All the moves
needed to obtain a missing article, without having to leave the
summary buffer.

Re: Oort, agent - fetching read articles

[Lars Magne Ingebrigtsen]

Harry Putnam <reader@newsguy.com> writes:

> This would allow user to mark %, go plugged, and J u.  All the moves
> needed to obtain a missing article, without having to leave the
> summary buffer.

Good idea.  I've now added this, although I rolled the "go plugged"
into `J u'.  (I did the same for the group buffer.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Oort, agent - fetching read articles

[Harry Putnam]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > This would allow user to mark %, go plugged, and J u.  All the moves
> > needed to obtain a missing article, without having to leave the
> > summary buffer.
> 
> Good idea.  I've now added this, although I rolled the "go plugged"
> into `J u'.  (I did the same for the group buffer.)

coolio  ... thanks