Gnus development mailing list
 help / color / mirror / Atom feed
From: George J McNinch <McNinch.1@nd.edu>
Cc: George McNinch <George.J.McNinch.1@nd.edu>,
	John Palmieri <Palmieri.2@nd.edu>
Subject: expiry/time-since problem
Date: 10 Dec 1998 12:09:59 -0500	[thread overview]
Message-ID: <yvz34sr3rkig.fsf@galois.math.nd.edu> (raw)

I posted a related question a few days ago to gnu.emacs.gnus thinking
that I was just being dumb and had some incorrect settings, but have
investigated a bit more and think I've found the problem.

I'm using pgnus-0.64. I'm getting incorrect behaviour
expiring/expunging mail. Playing with edebug, it turns out that in

nnmail-expired-article-p

the crucial test seems to occur here:

(condition-case ()
 (time-less-p days (time-since time))
(error nil))

Where time seems to be a string like:

"From <sender> <date> <time>"

Watching the results, it seems that time-since is returning tuples the
first coordinate of which are occasionally _large_ negative integers
(Well, ok large in absolute value) for dates that are a few days or
weeks old.

Here are some sample calculations!

(setq foo "From George.J.McNinch.1@nd.edu   Fri Nov 20 09:44:23 1998")
(setq bar "From George   Fri Nov 20 09:44:23 1998")
(setq ack "From George.1  Fri Nov 20 09:44:23 1998")

(time-since foo)
=> (-10543 13110)

(time-since bar)
=> (26 31953)

(time-since ack)
=> (-10543 13349)

This seems to clearly be the culprit for my expiration troubles.

Presumably the problem is in (?) date-to-time, or parse-time-string,
or some parsing function in parse-time.el.

I'll look at them a bit, but I'm sure someone else will have a better
idea of how to fix 'em.

Best,
George McNinch


             reply	other threads:[~1998-12-10 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-10 17:09 George J McNinch [this message]
1998-12-10 18:51 ` George J McNinch
1998-12-13  8:43   ` 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=yvz34sr3rkig.fsf@galois.math.nd.edu \
    --to=mcninch.1@nd.edu \
    --cc=George.J.McNinch.1@nd.edu \
    --cc=Palmieri.2@nd.edu \
    /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).