From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: Timer errors in last few days (bignump change?) Date: Wed, 5 Sep 2018 14:49:37 -0400 Message-ID: References: <83bm9byea6.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000032b22a0575243dd8" X-Trace: blaine.gmane.org 1536173277 26361 195.159.176.226 (5 Sep 2018 18:47:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 5 Sep 2018 18:47:57 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 05 20:47:53 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fxcqG-0006hV-Ue for ged-emacs-devel@m.gmane.org; Wed, 05 Sep 2018 20:47:53 +0200 Original-Received: from localhost ([::1]:57715 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fxcsM-0004sr-Oc for ged-emacs-devel@m.gmane.org; Wed, 05 Sep 2018 14:50:02 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37143) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fxcsD-0004sk-GR for emacs-devel@gnu.org; Wed, 05 Sep 2018 14:49:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fxcsC-0002TN-Q5 for emacs-devel@gnu.org; Wed, 05 Sep 2018 14:49:53 -0400 Original-Received: from mail-lf1-x135.google.com ([2a00:1450:4864:20::135]:43209) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fxcsB-0002RI-8p; Wed, 05 Sep 2018 14:49:51 -0400 Original-Received: by mail-lf1-x135.google.com with SMTP id h64-v6so6885057lfi.10; Wed, 05 Sep 2018 11:49:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9bI+jsLUsy6BaiUT4IbAlHisHLZqYIMwvvTR8YaiTFs=; b=tyFLGTrifspJK4SPLUBk3HfzB8RBqwIhc9wmBgBsaPyHjtQ63DddJF+/T29sXh5JLQ XuXixOS+l1bot0kBX3YjPEI9ubfWJjDTIDC6W5oAWMoWyIzKzqwVC/BRFzGkfgj6ThYl r8yycX7DFpd2KE3GnEarY/Iy3/ZilmxCNcP/blj+FXQjh4iO54yaLtoV418/XjE1pvgZ 7+dfWyCcmwCWa5sLkzuw1JnuIi45DG1kV0l0DWOhL5M/tDlPGn+Dfk3dROciHsnQ7wZe SJaMrNMJHtnVYxKJhC7yT+oQy6ttLlqXBybM9dxLetnLG7O7rjop2l8lb7ZR6h05ja+O XWQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9bI+jsLUsy6BaiUT4IbAlHisHLZqYIMwvvTR8YaiTFs=; b=qiUZSIEaGwJagqPJ0M3zVbxoYZ3ZJ5spZqT/l3fXiWDc6eN58leK0GABnYN1vUSEsJ Esndt8PBER2sAV5nZci8wvopEOTIeW6bBCxebNu0yHzHlw41o/1uCCFYcRqRpZnmGcv0 OyelGZfPD87nLZIRkINP/ctKUraPF14mf1B2lKL3rJP7zWHTTy/jAM/fam9I1r2csGiE 7qKCCUJCWhY2o5fd1orKrdNKK0Yf+WiHxun62JUma4lAw8eJzj3EyAFKveFmYW/cqzz3 8b55nC5Ep6IO3tMRLKZa8FvXYudj0QYszgi+KQd1khFmXwrTKsoBhI2dpu7vAEq2MwbF 3pBg== X-Gm-Message-State: APzg51BSZOAUvlsJFT09517Z7iYFVDdceW3pYnOcSzfWYHkWUMqrP9yH YKfCoci868ppYqGcwdRk/ekCkYJHPALPFX8bLMu3CQ== X-Google-Smtp-Source: ANB0VdakdB+Qz/hXEyuWc1W2niJLT69BXKKaSgwmUIt9VxoJECHuvc+RpfmmteNLKoob8SijuUsXNEyXJyfE6FGsFs8= X-Received: by 2002:a19:1517:: with SMTP id l23-v6mr25666671lfi.69.1536173389556; Wed, 05 Sep 2018 11:49:49 -0700 (PDT) In-Reply-To: <83bm9byea6.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::135 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:229310 Archived-At: --00000000000032b22a0575243dd8 Content-Type: text/plain; charset="UTF-8" On Wed, Sep 5, 2018 at 2:45 PM Eli Zaretskii 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 --00000000000032b22a0575243dd8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Sep 5,= 2018 at 2:45 PM Eli Zaretskii <eliz@gnu= .org> wrote:
=C2=A0

Kaushal Modi

--00000000000032b22a0575243dd8--