Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Continuing struggle with expiry
Date: Mon, 05 Aug 2002 14:42:46 +0200	[thread overview]
Message-ID: <ilu1y9dpjcp.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87bs8hxz7l.fsf@nwalsh.com> (Norman Walsh's message of "Mon, 05 Aug 2002 08:33:02 -0400")

Norman Walsh <ndw@nwalsh.com> writes:

> / prj@po.cwru.edu (Paul Jarc) was heard to say:
> | Norman Walsh <ndw@nwalsh.com> wrote:
> |> What function actually cleans up articles marked expired that are older
> |> than expiry-wait days?
> |
> | nn*-request-expire-articles.
>
> Uncle! I like to think I enjoy elisp hackery as much as the next guy,
> but the more I investigate this problem, the less sense it makes.
>
> Expiry isn't working for me because nnml-request-expire-articles calls
> nnmail-expired-article-p with mod-time set to '(15679 803). And when
> nnmail-expired-article-p asks for the (time-since '(15679 803)), time-since
> goes bang:
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>   time-since((15679 803))
>   eval((time-since (quote (15679 803))))
>
> That is, the byte-compiled, auto-loaded version of time-since goes
> bang. If I copy the definition of time-since into *scratch* and
> compile it myself, which I did initially in order to debug it further,
> it runs just fine, thank you very much.

Are you using the correct time-since?  I think a problem like this was
solved in time-date.el a few months ago, so if you have an older byte
compiled version still laying around somewhere, perhaps your emacs
uses the wrong one.  Try C-h f time-since in a fresh Gnus.




  reply	other threads:[~2002-08-05 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 15:07 Norman Walsh
2002-08-02 17:20 ` Paul Jarc
2002-08-05 12:33   ` Norman Walsh
2002-08-05 12:42     ` Simon Josefsson [this message]
2002-08-05 14:52       ` Norman Walsh
2002-08-05 15:44         ` Kai Großjohann
2002-08-02 18:09 ` Kai Großjohann

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=ilu1y9dpjcp.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).