Re: Timer errors in last few days (bignump change?)

[Kaushal Modi]

When I try to do this:

M-: (apply #'encode-time (parse-time-string "2018-09-05"))

I get:

Debugger entered--Lisp error: (wrong-type-argument fixnump nil)

  encode-time(nil nil nil 5 9 2018 nil nil nil)
  apply(encode-time (nil nil nil 5 9 2018 nil nil nil))
  eval((apply #'encode-time (parse-time-string "2018-09-05")) t)
  eval-_expression_((apply #'encode-time (parse-time-string "2018-09-05")) nil nil 127)
  funcall-interactively(eval-_expression_ (apply #'encode-time (parse-time-string "2018-09-05")) nil nil 127)
  call-interactively(eval-_expression_ nil nil)
  command-execute(eval-_expression_)

On Wed, Sep 5, 2018 at 1:54 PM Kaushal Modi <address@hidden> wrote:

Hello,

I have been building Emacs regularly from the master branch.

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?).

Before I dig deeper into debugging if some package went rogue, do you think this number-or-marker-p error is related to bignump changes under the hood?

--

Kaushal Modi

--

Kaushal Modi