Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: gnus-agent-expire seems to expire more messages than it should?
Date: Tue, 22 Jan 2013 16:30:33 +1030	[thread overview]
Message-ID: <87fw1tkb9a.fsf@ucl.ac.uk> (raw)

Hello,

at some point recently, I realised that my agent directory was using up
over 2GB.  Not a big deal, as such, but I thought I could clean things
up a little.  I had a look at gnus-agent-expire and realised that
expiration of articles did not necessarily clean up the agent cache.  So
I executed this function.  Success: I freed up a lot of space.

However, I seem to have freed up rather more than I expected.  I have

,----[ C-h v gnus-agent-expire-all RET ]
| gnus-agent-expire-all is a variable defined in `gnus-agent.el'.
| Its value is nil
| 
| Documentation:
| If non-nil, also expire unread, ticked and dormant articles.
| If nil, only read articles will be expired.
| 
| You can customize this variable.
| 
| [back]
`----

which tells me that only *read* articles would be expired.  The gnus
agent seems to have expired all kinds of read articles as well,
essentially behaving as if I had set gnus-agent-expire-all to something
other than nil.  Am I misunderstanding something or have I missed
another configuration variable?

I haven't lost anything, obviously, but all my expired *unread* articles
now need to be re-loaded.  No big deal but I am curious!

I am using gnus up-to-date from a day or so ago.

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 + Ma Gnus v0.6
: BBDB version 3.02 ($Date: 2013/01/13 22:41:36 $)




             reply	other threads:[~2013-01-22  6:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  6:00 Eric S Fraga [this message]
2013-01-22  6:41 ` Eric S Fraga
2013-08-01 21:48 ` Lars Magne Ingebrigtsen

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=87fw1tkb9a.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=ding@gnus.org \
    /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).