From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,
74870-done@debbugs.gnu.org,
Jan Jouleodov <jouleodov@protonmail.com>
Subject: bug#74870: cl-labels and cl-flet don't create named blocks
Date: Wed, 1 Jan 2025 19:32:46 -0600 [thread overview]
Message-ID: <CADwFkmmofBb4B56LMX7wstDLTZo0=K8WCNZjMCgZQjSHLU6Qiw@mail.gmail.com> (raw)
In-Reply-To: <jwvikrdf1z8.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 21 Dec 2024 11:14:54 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Is there any reason why one would not want to *always* emulate the CL
>>> behavior in cl-lib? I could only think of a backward compatibility
>>> problem before CL was standardized, but I am not familiar with the time
>>> frame of cl-lib to know if that's really the case.
>> Could you try the patch below?
>
> Never mind, it here's a better one I just pushed to `master`.
I'm therefore closing this bug report.
next prev parent reply other threads:[~2025-01-02 1:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 23:30 bug#74870: cl-labels and cl-flet don't create named blocks Jan Jouleodov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-14 16:54 ` Eli Zaretskii
2024-12-17 3:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 0:55 ` Jan Jouleodov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 15:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 16:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 16:24 ` Jan Jouleodov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 1:32 ` Stefan Kangas [this message]
2024-12-19 16:28 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkmmofBb4B56LMX7wstDLTZo0=K8WCNZjMCgZQjSHLU6Qiw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=74870-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jouleodov@protonmail.com \
--cc=monnier@iro.umontreal.ca \
/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.