Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: [Q]: Agent expiration and fetching
Date: Wed, 13 Oct 2004 07:58:45 -0400	[thread overview]
Message-ID: <ufz4ig77u.fsf@vignette.com> (raw)
In-Reply-To: <plop87wtxvxesu.fsf@gnu-rox.org>

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



  reply	other threads:[~2004-10-13 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 23:29 Xavier Maillard
2004-10-13  2:40 ` Kevin Greiner
2004-10-13  7:22   ` Xavier Maillard
2004-10-13 11:58     ` Kevin Greiner [this message]
2004-10-13 13:03 ` Steinar Bang
2004-10-13 14:39   ` Xavier Maillard

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=ufz4ig77u.fsf@vignette.com \
    --to=kevin.greiner@vignette.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).