From: Paul Eggert <eggert@cs.ucla.edu>
To: Kaushal Modi <kaushal.modi@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Timer errors in last few days (bignump change?)
Date: Wed, 5 Sep 2018 15:34:13 -0700 [thread overview]
Message-ID: <2e6d44fa-3520-c74a-4625-d8c401cfb078@cs.ucla.edu> (raw)
In-Reply-To: <CAFyQvY2+KiDWX_GzLC7866s+mS77STT7mRYTimYpy5VkvLZFHQ@mail.gmail.com>
Kaushal Modi wrote:
> In the last 2-3 days, this new error starts popping up frequently.
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
> timer-next-integral-multiple-of-time((63065 20560) 60)
> display-time-event-handler()
> apply(display-time-event-handler nil)
> timer-event-handler([t 23440 6080 0 60 display-time-event-handler nil nil
> 0])
>
> timer-next-integral-multiple-of-time accepts TIME and SECS (integer) as
> arguments, and the values (63065 20560) and 60 seem fine (or not?).
I don't see how the first argument of timer-next-integral-multiple-of-time could
be (63065 20560). display-time-event-handler passes the value returned by
current-time, and that value is always a list of four integers. Is it possible
that you've redefined current-time, or redefined display-time-event-handler?
(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.
What platform are you running on? What is time_t on that platform, exactly? How
did you configure Emacs? Perhaps this is related to the year-2100 problems on
DOS and MS-Windows. I don't know much about those problems, though. See:
https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2100
next prev parent reply other threads:[~2018-09-05 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 17:54 Timer errors in last few days (bignump change?) Kaushal Modi
2018-09-05 18:39 ` Kaushal Modi
2018-09-05 18:43 ` Noam Postavsky
2018-09-05 18:45 ` Eli Zaretskii
2018-09-05 18:49 ` Kaushal Modi
2018-09-05 18:53 ` Kaushal Modi
2018-09-05 19:23 ` Eli Zaretskii
2018-09-05 22:34 ` Paul Eggert [this message]
2018-09-05 22:44 ` Kaushal Modi
2018-09-05 22:55 ` Kaushal Modi
2018-09-05 23:28 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e6d44fa-3520-c74a-4625-d8c401cfb078@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).