Re: gnus won't cache articles retrieved with gnus-summary-refer-parent-article (`^')

Re: gnus won't cache articles retrieved with gnus-summary-refer-parent-article (`^')

[RL]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> RL <alcoco@carrotmail.com> writes:
> 
> > Pressing `^' in a summary buffer runs
> > `gnus-summary-refer-parent-article' which retrieves a parent post.
> > But what if I want to add this parent to the cache (using `*' which
> > runs `gnus-cache-enter-article')? gnus tells me it can't cache article
> > -1.
> >
> > Is this a bug, or is there some way to cache such articles?

> This is a missing feature.  A workaround would be to C-u 9 9 9 M-g
> in the group (which fetches 999 articles by number) and then do `^'
> and hope that your article was amongst these.  If not, try larger
> numbers.  This is slow.

ah OK. that would have worked for the particular instance I was
thinking of anyway.  In fact I just forwarded the message
to myself and cached the new copy (though with your way it owuld have
been in the right group--a news group).

But how come gnus can't operate on the retrieved messages? For
caching, couldnt gnus just save the message in a file?

Anyway thanks for the advice from everyone who responded.

Re: gnus won't cache articles retrieved with gnus-summary-refer-parent-article (`^')

[Kai Großjohann]

RL <alcoco@carrotmail.com> writes:

> But how come gnus can't operate on the retrieved messages? For
> caching, couldnt gnus just save the message in a file?

Gnus wants to use the article number as the file name (to make sure
the file name is unique, and to know the order of the messages).  If
Gnus doesn't know the article number, it cries bloody murder...

But as those who have no need of a name said, this has been fixed in
Oort Gnus: that version tries to glean the article number from the
Xref header.

kai
-- 
Silence is foo!