On Wed, Sep 5, 2018 at 6:44 PM Kaushal Modi <kaushal.modi@gmail.com> wrote:

On Wed, Sep 5, 2018, 6:34 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
Kaushal Modi wrote:

(63065 20560) corresponds to 2100-12-21 05:00:00 UTC, which is pretty far in the
future, and it seems unlikely you'd want to set alarms for that timestamp.

Oh, thank you! I inadvertently played some "Back from the Future" while hacking with a package test suite to fake the current-time.

Sorry for your wasted time. It was my mistake.. I redefined current-time.

Though.. that value even though way in future is still valid, right? It just happens that (encode-time 0 0 0 21 12 2100) returns that 2 element time list.

Is the issue with:

- time list having 2 elements?

- year being 2100?

- Or the delta between that fake `current-time' and real current-time too big?

I am on RHEL 6.8.