From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: ulm@gentoo.org, monnier@iro.umontreal.ca, 73596@debbugs.gnu.org
Subject: bug#73596: 29.4; empty (let) does not signal an error
Date: Sun, 27 Oct 2024 12:22:19 +0200 [thread overview]
Message-ID: <86msipalr8.fsf@gnu.org> (raw)
In-Reply-To: <874j5hs2mn.fsf@igel.home> (message from Andreas Schwab on Sat, 12 Oct 2024 18:32:48 +0200)
Ping! What should we do with this bug report? Close it?
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii
> <eliz@gnu.org>, 73596@debbugs.gnu.org
> Date: Sat, 12 Oct 2024 18:32:48 +0200
>
> On Okt 12 2024, Ulrich Mueller wrote:
>
> >>>>>> 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.
>
> That's because does the same.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
> "And now for something completely different."
>
next prev parent reply other threads:[~2024-10-27 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 12:54 bug#73596: 29.4; empty (let) does not signal an error Ulrich Mueller
2024-10-12 11:26 ` Eli Zaretskii
2024-10-12 13:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 13:54 ` Ulrich Mueller
2024-10-12 14:21 ` Andreas Schwab
2024-10-12 15:40 ` Ulrich Mueller
2024-10-12 15:51 ` Andreas Schwab
2024-10-12 15:57 ` Ulrich Mueller
2024-10-12 16:32 ` Andreas Schwab
2024-10-13 5:04 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 10:22 ` Eli Zaretskii [this message]
2024-10-27 10:49 ` Andreas Schwab
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=86msipalr8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73596@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
--cc=ulm@gentoo.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.