From: Ted Stern <dodecatheon@gmail.com>
Subject: Re: Total expiry not working -- is clock skew the problem?
Date: Thu, 09 Feb 2006 13:29:02 -0800 [thread overview]
Message-ID: <lsp64noxlup.fsf@drip.ca.boeing.com> (raw)
In-Reply-To: <b4mlkwlwd2p.fsf@jpl.org>
On 8 Feb 2006 at 17:11 UTC-0800, Katsumi Yamaoka wrote:
> That's exactly the cause of your problem. Nnfolder will never
> expire articles if that function doesn't work. You seem to use
> `time-since' defined in some Lisp module other than time-date.el.
> For example, it is make-regexp.el:
>
> http://cvs.sourceforge.net/viewcvs.py/tei/tei-emacs/tei-emacs/Attic/make-regexp.el?rev=1.2
>
> I could reproduce the same error with it.
Bingo! You pegged it.
> If you're using such one, you can replace it with another one which
> doesn't contain time-* functions. For instance:
>
> https://svn.r-project.org/ESS/trunk/lisp/make-regexp.el
Okay, I snagged this one.
>
> Other possible solutions include:
>
> 1. Don't use it.
Not practical in the near term.
> 2. Load time-date.el explicitly.
> 3. Putting the following form in your ~/.emacs file (or
> ~/.gnus.el file) might do the trick.
>
> (defadvice time-since (around reload-time-date_el activate)
> "Reload time-date.el if this function seems to have been overridden."
> (condition-case nil
> ad-do-it
> (error
> (load "time-date")
> ad-do-it)))
I did this for good measure (in ~/.gnus), just before the call to
make-regexp :-)
>
>>> BTW, expiring might be executed in your machine eight hours earlier
>>> than the time specified with expiry-wait. It is because the
>>> timestamp in the X-Gnus-Article-Number header is made by the
>>> current-time-string function and doesn't have a timezone info. For
>>> instance:
>
> I've modified nnfolder.el so as to use `message-make-date' which
> generates a timezone info rather than `current-time-string' when
> generating X-Gnus-Article-Number header.
Excellent, another good fix! I'll update my CVS gnus also.
Ted Stern
--
dodecatheon at gmail dot com
Frango ut patefaciam -- I break so that I may reveal
next prev parent reply other threads:[~2006-02-09 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 16:28 Ted Stern
2006-02-07 17:24 ` Ted Stern
2006-02-08 3:37 ` Katsumi Yamaoka
2006-02-08 20:49 ` Ted Stern
2006-02-09 1:11 ` Katsumi Yamaoka
2006-02-09 21:29 ` Ted Stern [this message]
2006-02-08 20:56 ` Ted Stern
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=lsp64noxlup.fsf@drip.ca.boeing.com \
--to=dodecatheon@gmail.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).