GNU bug report logs - #73596
29.4; empty (let) does not signal an error

Previous Next

Package: emacs;

Reported by: Ulrich Mueller <ulm <at> gentoo.org>

Date: Wed, 2 Oct 2024 12:55:02 UTC

Severity: normal

Tags: wontfix

Found in version 29.4

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Ulrich Mueller <ulm <at> gentoo.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: Ulrich Mueller <ulm <at> gentoo.org>, Eli Zaretskii <eliz <at> gnu.org>, Stefan Monnier <monnier <at> iro.umontreal.ca>, 73596 <at> debbugs.gnu.org
Subject: bug#73596: 29.4; empty (let) does not signal an error
Date: Sat, 12 Oct 2024 17:57:03 +0200

>>>>> On Sat, 12 Oct 2024, Andreas Schwab wrote:

> On Okt 12 2024, Ulrich Mueller wrote:
>> $ emacs -Q
>> M-: (let) RET
>> ⇒ nil

> Don't use eval-expression.  It does not evaluate the form, but something
> else.

Well, it's the same with eval-last-sexp. And behavior has definitely
changed, with Emacs 29.4 (as well as 31.0.50) I see a nil result, while
with Emacs 27.2 I get:

Debugger entered--Lisp error: (wrong-number-of-arguments let 0)
  (let)
  (progn (let))
  eval((progn (let)) t)
  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)
This bug report was last modified 199 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.