From: Max Froumentin <max@lapin-bleu.net>
Subject: bug in nnfolder-request-expire-articles
Date: Tue, 21 Feb 2006 12:09:39 +0000 [thread overview]
Message-ID: <87acck52ws.fsf@lapin-bleu.net> (raw)
nnfolder.el CVS-7.16 (i.e. latest as of this email)
nnfolder-request-expire-articles has a comment that says:
;; Since messages are sorted in arrival order and expired in the
;; same order, we can stop as soon as we find a message that is
;; too old.
That's not true in some (admittedly twisted, but it happened to me)
circumstances: the messages are sorted in arrival order, but that
doesn't mean that they are sorted in date order. What happened to me
is that I mistakenly set my computer's date months ahead in the
future, and received some emails, then realised my mistake and
corrected the system's date. That meant that the messages were indeed
sorted in arrival order but not by date.
When nnfolder-request-expire-articles expired articles, it found the
first in arrival order wasn't to be expired, because it wasn't old enough,
and thus it stopped and never checked the next articles.
The best fix would be along the lines of sorting the expirable
articles by date and not by number in
gnus-summary-expire-articles. But it would be slower, and I don't know
if we should bother given the small importance of the bug (it always
resolves eventually, as soon as the first article in the list becomes
expirable, and it only becomes an annoyance if the date has been off
by a long time).
Max.
next reply other threads:[~2006-02-21 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 12:09 Max Froumentin [this message]
2006-04-12 5:57 ` 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=87acck52ws.fsf@lapin-bleu.net \
--to=max@lapin-bleu.net \
/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).