[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Questions about expiring
From: |
Cecil Westerhof |
Subject: |
Questions about expiring |
Date: |
Fri, 04 Dec 2009 08:30:23 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) |
Because the hint from Nicolas KOWALSKI it is not as important anymore,
but I like to understand things.
First when leaving a group gnus-summary-expire-articles was always
called. I had two big groups (on a local IMAPS server): one with 1162
articles off which 71 where expired and one with 8228 articles of which
54 where expired. The first group took a lot longer as the first. When
things had to be deleted from the IMAPS server, I could understand
it. But when leaving a group 2 minutes later (and when there where no
articles to be deleted) I do not understand this. So why is this the
case?
By the way: to get the number of articles that are expired in a group:
- enter it with C-u Space
- M-x how-many
- ^E
With apropos I get:
gnus-agent-expire-days is a variable defined in `gnus-agent.el'.
Its value is 7
Documentation:
Read articles older than this will be expired.
I think that this is an error, because -luckily- only articles from
which I have said that they are expired more then seven days ago are
deleted.
Is there a way to find out how long ago I expired an article?
When running gnus-group-expire-all-groups I would like to log how many
articles from a group are deleted. Is this possible?
When running gnus-group-expire-all-groups. A lot of information is
displayed in the mini-buffer, but not everything is logged in the
Message buffer. For example the connection information to the IMAPS
server. Is there a way to capture all the information?
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
- Questions about expiring,
Cecil Westerhof <=