gnus-agent-fetch-selected-article no longer caches articles

gnus-agent-fetch-selected-article no longer caches articles

[Steinar Bang]

Platform: Intel Atom, Linpus linux (FC8 derivative)
	  GNU Emacs 22.1.1 (i386-redhat-linux-gnu, GTK+ Version 2.12.1) of 2007-10-24 on xenbuilder2.fedora.redhat.com
	  No Gnus v0.11 (CVS update from June 13)

I have the following in ~/.gnus.el to make all read articles be stored
in agent:

 ;; Store article in agent when reading it while online
 (add-hook 'gnus-select-article-hook 'gnus-agent-fetch-selected-article)

But it no longer works.

Does anyone know why?

Thanx!


- Steinar

Is there some kind of agent expiry now? (Was: gnus-agent-fetch-selected-article no longer caches articles)

[Steinar Bang]

>>>>> Steinar Bang <sb@dod.no>:

> Platform: Intel Atom, Linpus linux (FC8 derivative)
> 	  GNU Emacs 22.1.1 (i386-redhat-linux-gnu, GTK+ Version 2.12.1) of 2007-10-24 on xenbuilder2.fedora.redhat.com
> 	  No Gnus v0.11 (CVS update from June 13)

> I have the following in ~/.gnus.el to make all read articles be stored
> in agent:

>  ;; Store article in agent when reading it while online
>  (add-hook 'gnus-select-article-hook 'gnus-agent-fetch-selected-article)

> But it no longer works.

Looking at a cache directory, eg. the directory for
gmane.emacs.gnus.general, it contains articles, but it only contains
fairly recent articles:

  /home/user/News/agent/nntp/news.gmane.org/gmane/emacs/gnus/general:
  total used in directory 244 available 3628336
  drwxrwxr-x 2 user user   4096 2009-07-01 17:58 .
  drwxrwxr-x 3 user user   4096 2009-06-13 01:24 ..
  -rw-rw-r-- 1 user user   3318 2009-06-13 01:24 68608
  -rw-rw-r-- 1 user user   6252 2009-06-13 01:24 68610
  -rw-rw-r-- 1 user user   7051 2009-06-13 01:24 68611
  -rw-rw-r-- 1 user user   4324 2009-06-19 17:41 68612
  -rw-rw-r-- 1 user user   4998 2009-06-19 17:27 68614
  -rw-rw-r-- 1 user user   3498 2009-06-19 17:27 68616
  -rw-rw-r-- 1 user user   3750 2009-06-19 17:41 68617
  -rw-rw-r-- 1 user user   4158 2009-06-19 17:27 68618
  -rw-rw-r-- 1 user user   3620 2009-06-19 17:27 68620
  -rw-rw-r-- 1 user user   4220 2009-06-19 19:13 68621
  -rw-rw-r-- 1 user user   3408 2009-06-20 18:22 68622
  -rw-rw-r-- 1 user user   4888 2009-06-22 14:24 68623
  -rw-rw-r-- 1 user user   2650 2009-06-23 10:24 68624
  -rw-rw-r-- 1 user user   2496 2009-06-23 10:25 68625
  -rw-rw-r-- 1 user user   4552 2009-06-25 09:27 68626
  -rw-rw-r-- 1 user user   3393 2009-06-25 09:27 68627
  -rw-rw-r-- 1 user user   3760 2009-06-25 12:46 68628
  -rw-rw-r-- 1 user user   3916 2009-06-25 09:28 68629
  -rw-rw-r-- 1 user user   3947 2009-06-30 19:55 68630
  -rw-rw-r-- 1 user user   4077 2009-06-30 19:55 68631
  -rw-rw-r-- 1 user user   4088 2009-07-01 17:58 68632
  -rw-rw-r-- 1 user user   2817 2009-07-01 17:58 .agentview
  -rw-rw-r-- 1 user user 114596 2009-07-01 17:58 .overview

I'll keep a watch to see if this changes over time.

But even without that confirmation, what only having recent articles
made me start to wonder about, is if there is a new agent expiry
mechanism in place?

Does anyone know?

The manual still states the same old text, ie.

 The Agent back end, `nnagent', doesn't handle expiry.  Well, at least
 it doesn't handle it like other back ends.  Instead, there are special
 `gnus-agent-expire' and `gnus-agent-expire-group' commands that will
 expire all read articles that are older than `gnus-agent-expire-days'
 days.

Is that command now run automatically?  And has it stopped not expiring
ticked articles?  Or has it in fact always expired ticked articles?

Thanx!


- Steinar