From: Michael Brand <email@example.com>
To: Carsten Dominik <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>
Subject: Re: Agenda Bulk Scatter bug
Date: Fri, 10 Jun 2011 23:32:40 +0200 [thread overview]
Message-ID: <BANLkTi=fE01wTYDwV=oR3s43tUWJNF4NqA@mail.gmail.com> (raw)
On Fri, Jun 10, 2011 at 10:20, Carsten Dominik
> When I evaluate this form
> (decode-time (days-to-time (time-to-days (current-time))))
> I get a date in the year 3980. I think this used to work.
> Is there anyone who has an idea what is going on here?
Same here (except the "I think this used to work") on GNU Emacs 23.3.1
x86_64-apple-darwin that is 64 bit and has also the famous time_t with
64 bits. The error reported by others comes from time_t with 32 bits.
decode-time checks for overflow of time_t before either passing it to
the system call localtime(const time_t *), or giving the error.
But since it's only a mismatch of current-time with base 1970 and
time-to-days with base 1bec, is
(decode-time (days-to-time (- (time-to-days (current-time))
(time-to-days '(0 0)))))
what you need? Why the *days* function, for some rounding?
next prev parent reply other threads:[~2011-06-10 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 4:54 Agenda Bulk Scatter bug Robert Cunningham
2011-06-08 12:33 ` Christian Egli
2011-06-10 8:20 ` Carsten Dominik
2011-06-10 9:05 ` David Edmondson
2011-06-14 8:41 ` Carsten Dominik
2011-06-14 8:51 ` Carsten Dominik
2011-06-10 19:16 ` Achim Gratz
2011-06-10 19:51 ` Nick Dokos
2011-06-10 21:32 ` Michael Brand [this message]
2011-06-11 8:43 ` Robert Cunningham
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).