[Q]: Agent expiration and fetching

[Q]: Agent expiration and fetching

[Xavier Maillard]

Hello,

I want to ask something which tends to make me crazy.

I set the gnus-agent-expiration to enabled. It expires correctly
but I sometimes, when 'J s'ing got old messages just downloaded
again.

How can I prevent this from happening ?

Subsidiary question: how can I cache all articles automatically ?

I, for instance, use this setting:

,----[ C-h v gnus-cache-enter-articles RET ]
| gnus-cache-enter-articles's value is 
| (ticked dormant unread)
| 
| 
| Classes of articles to enter into the cache.
| 
| You can customize this variable.
| 
| Defined in `gnus-cache'.
| 
| [back]
`----

I thought it was enough, but it seems it is not.

And last, what is best to use: ticked/dormant articles or
cached ? (given the fact I have almost all agentized).

Thank you.
-- 
.o.                     | zedek (at) gnu-rox.org
..o Hacker Wonderland   | 
ooo                     | 

Re: [Q]: Agent expiration and fetching

[Kevin Greiner]

Xavier Maillard <zedek@gnu-rox.org> writes:

> Hello,
>
> I want to ask something which tends to make me crazy.
>
> I set the gnus-agent-expiration to enabled. It expires correctly
> but I sometimes, when 'J s'ing got old messages just downloaded
> again.
>
> How can I prevent this from happening ?

Set gnus-agent-consider-all-articles to nil.


> Subsidiary question: how can I cache all articles automatically ?

The cache and the agent are redundant in that both create independent
local copies of your articles.  Are you sure that you want to do this?

> And last, what is best to use: ticked/dormant articles or
> cached ? (given the fact I have almost all agentized).

Personally, I either set a group to never expire from the agent (in
which case I never cache those articles) or I expire after a short
time but use the cache for long term storage.  Which I do depends upon
the percentage of articles that I expect to keep in a certain group.

Kevin

Re: [Q]: Agent expiration and fetching

[Xavier Maillard]

On 13 oct 2004, Kevin Greiner wrote:

> Xavier Maillard <zedek@gnu-rox.org> writes:
> 
> > Hello,
> > 
> > I want to ask something which tends to make me crazy.
> > 
> > I set the gnus-agent-expiration to enabled. It expires
> > correctly but I sometimes, when 'J s'ing got old messages
> > just downloaded again.
> > 
> > How can I prevent this from happening ?
> 
> Set gnus-agent-consider-all-articles to nil.

Hmm:

,----[ C-h v gnus-agent-consider-all-articles RET ]
| gnus-agent-consider-all-articles's value is nil
| 
| [back]
`----
 
> > Subsidiary question: how can I cache all articles
> > automatically ?
> 
> The cache and the agent are redundant in that both create
> independent local copies of your articles. Are you sure that
> you want to do this?

Well, the goal is not to have redundant stuff but, as I
experiment things, I would like to be sure I do not loose
anything.

So the main idea, for instance, is to enter *ALL* unread/unseen
articles into the cache even if I already have fetched them in
the agent.

I tried this:

,----[ C-h v gnus-cache-enter-articles RET ]
| gnus-cache-enter-articles's value is 
| (ticked dormant unread unseen)
| 
| 
| Classes of articles to enter into the cache.
| 
| You can customize this variable.
| 
| Defined in `gnus-cache'.
| 
| [back]
`----

But that doesn't work.

Oh, and yes, I remove articles when read or expired from the
cache off course :/

What is wrong with this ?
 
> > And last, what is best to use: ticked/dormant articles or
> > cached ? (given the fact I have almost all agentized).
> 
> Personally, I either set a group to never expire from the agent
> (in which case I never cache those articles) or I expire after
> a short time but use the cache for long term storage. Which I
> do depends upon the percentage of articles that I expect to
> keep in a certain group.

Thank you for your feedback. There so many features I never ever
have visited before, I am almost thinking I am n00b :/

Regards.
-- 
GNUSFR.ORG                       http://gnusfr.org/
EMACSFR.ORG                      http://emacsfr.org/
Xavier Maillard                  Tel: +33 6 68 04 64 37

Re: [Q]: Agent expiration and fetching

[Kevin Greiner]

Xavier Maillard <zedek@gnu-rox.org> writes:

> On 13 oct 2004, Kevin Greiner wrote:
>
>> Xavier Maillard <zedek@gnu-rox.org> writes:
>> 
>> > Hello,
>> > 
>> > I want to ask something which tends to make me crazy.
>> > 
>> > I set the gnus-agent-expiration to enabled. It expires
>> > correctly but I sometimes, when 'J s'ing got old messages
>> > just downloaded again.
>> > 
>> > How can I prevent this from happening ?
>> 
>> Set gnus-agent-consider-all-articles to nil.
>
> Hmm:
>
> ,----[ C-h v gnus-agent-consider-all-articles RET ]
> | gnus-agent-consider-all-articles's value is nil
> | 
> | [back]
> `----

Now that is unfortunate.  You'll have to debug to figure this one out.
The critical function is gnus-agent-fetch-headers.  The only problem
is that with gnus-agent-consider-all-articles set to nil, the only
articles being fetched by the agent are unread articles.  That would
seem to exclude your old articles so...

>> > Subsidiary question: how can I cache all articles
>> > automatically ?
>> 
>> The cache and the agent are redundant in that both create
>> independent local copies of your articles. Are you sure that
>> you want to do this?
>
> Well, the goal is not to have redundant stuff but, as I
> experiment things, I would like to be sure I do not loose
> anything.
>
> So the main idea, for instance, is to enter *ALL* unread/unseen
> articles into the cache even if I already have fetched them in
> the agent.
>
> I tried this:
>
> ,----[ C-h v gnus-cache-enter-articles RET ]
> | gnus-cache-enter-articles's value is 
> | (ticked dormant unread unseen)
> | 
> | 
> | Classes of articles to enter into the cache.
> | 
> | You can customize this variable.
> | 
> | Defined in `gnus-cache'.
> | 
> | [back]
> `----
>
> But that doesn't work.
>
> Oh, and yes, I remove articles when read or expired from the
> cache off course :/
>
> What is wrong with this ?

Looking at the code, gnus-use-cache must be active (t).  The default
'passive will simply not do.  The cacheable filter,
gnus-cacheable-groups, must also be either set to null or a regexp
matching your group.
  
>> > And last, what is best to use: ticked/dormant articles or
>> > cached ? (given the fact I have almost all agentized).
>> 
>> Personally, I either set a group to never expire from the agent
>> (in which case I never cache those articles) or I expire after
>> a short time but use the cache for long term storage. Which I
>> do depends upon the percentage of articles that I expect to
>> keep in a certain group.
>
> Thank you for your feedback. There so many features I never ever
> have visited before, I am almost thinking I am n00b :/

Same here.

Kevin

Re: [Q]: Agent expiration and fetching

[Steinar Bang]

>>>>> Xavier Maillard <zedek@gnu-rox.org>:

> Subsidiary question: how can I cache all articles automatically ?

You mean cache them when reading them, using agent?

I'm just now trying to change the setting of gnus-select-article-hook
from the default nil, to the option provided by the defcustom,
ie. gnus-agent-fetch-selected-article. 

You can customize it with
	M-x customize-variable RET gnus-select-article-hook RET
and check off for gnus-agent-fetch-selected-article.

The IMAP server at work is down today, so I'm not able to _really_
test it out for myself, by reading some articles here, and checking at
home if they are still present when the this nnimap server is in
offline mode.

Re: [Q]: Agent expiration and fetching

[Xavier Maillard]

On 13 oct 2004, Steinar Bang wrote:

> > > > > > Xavier Maillard <zedek@gnu-rox.org>:
> 
> > Subsidiary question: how can I cache all articles
> > automatically ?
> 
> You mean cache them when reading them, using agent?

No, I mean cache them even if unseen or unread.

I uncache them when needed when they are read or I uncache them
explicitly.
 
Regards.
-- 
GNUSFR.ORG                       http://gnusfr.org/
EMACSFR.ORG                      http://emacsfr.org/
Xavier Maillard                  Tel: +33 6 68 04 64 37