all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Timer errors in last few days (bignump change?)
Date: Wed, 5 Sep 2018 14:49:37 -0400	[thread overview]
Message-ID: <CAFyQvY3WL98p9oXhvM9orUY3qO8zfZUFstAOZLaTBiOzV1KLWA@mail.gmail.com> (raw)
In-Reply-To: <83bm9byea6.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

On Wed, Sep 5, 2018 at 2:45 PM Eli Zaretskii <eliz@gnu.org> wrote:


> Are you saying that Emacs 26 doesn't signal a similar error in this
> case?  It does for me.
>

No, I did not imply that.

I just tried out on 26.1, and I get a similar error (integerp instead of
fixnump):

Debugger entered--Lisp error: (wrong-type-argument integerp 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 (function encode-time) (parse-time-string "2018-09-05")) nil)
  elisp--eval-last-sexp(nil)
  eval-last-sexp(nil)
  funcall-interactively(eval-last-sexp nil)
  call-interactively(eval-last-sexp nil nil)
  command-execute(eval-last-sexp)

So.. is this a user error.. that elisp is not valid (i.e. nil not allowed
in that list)?
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1300 bytes --]

  reply	other threads:[~2018-09-05 18:49 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 [this message]
2018-09-05 18:53       ` Kaushal Modi
2018-09-05 19:23         ` Eli Zaretskii
2018-09-05 22:34 ` Paul Eggert
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFyQvY3WL98p9oXhvM9orUY3qO8zfZUFstAOZLaTBiOzV1KLWA@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.