fwiw i ran this once:
;;(/ (org-time-string-to-seconds "--01-01 00:00") 60.0) 4222846500.0
;;(/ (org-time-string-to-seconds "-0001-12-31 00:00") 60.0) -1035068671.7
;; oops
;;(/ (org-time-string-to-seconds "-12-31 00:00") 60.0) -1035594271.7
;;(/ (org-time-string-to-seconds
Hello Richard,
On 2021-06-07 11:17, Richard Lawrence
writes:
> whoa, that's a weird behavior, but it seems not to be a bug. I learned
> something today!
>
> It looks like some Emacs implementations don't support dates after
> 2038-1-1, so Org doesn't let you specify them by default. See the
>
alan.schm...@polytechnique.org writes:
[...]
> I need to schedule something for 2039, but when I do it the date is set
> for 2037. I tried with a plain emacs config and I see the same issue. Is
> this a bug?
Sounds like the bug of 2038ยน. I assume that 32 bit integers are used
somewhere to
Hi Alan,
alan.schm...@polytechnique.org writes:
> I need to schedule something for 2039, but when I do it the date is set
> for 2037. I tried with a plain emacs config and I see the same issue. Is
> this a bug?
whoa, that's a weird behavior, but it seems not to be a bug. I learned
something
Hello,
I need to schedule something for 2039, but when I do it the date is set
for 2037. I tried with a plain emacs config and I see the same issue. Is
this a bug?
Best,
Alan
signature.asc
Description: PGP signature
