From: Michael Heerdegen <michael_heerdegen@web.de>
To: Richard Stallman <rms@gnu.org>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org,
Sean Whitton <spwhitton@spwhitton.name>
Subject: Re: master 2e9111813b: Add two classic Common Lisp macro-writing macros
Date: Sun, 17 Apr 2022 03:57:45 +0200 [thread overview]
Message-ID: <87v8v8mpye.fsf@web.de> (raw)
In-Reply-To: <E1nfD7U-000753-Ue@fencepost.gnu.org> (Richard Stallman's message of "Thu, 14 Apr 2022 23:59:40 -0400")
Richard Stallman <rms@gnu.org> writes:
> Why was it given that name? Is there a good reason for that to be its
> name?
Maybe because generalized variables once were implemented in cl, and
letf is about binding them?
> Should we rename it to `letf'?
Or maybe gv-letf, if we don't want to give it such a prominent name.
Michael.
next prev parent reply other threads:[~2022-04-17 1:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164974332528.14217.12591424007013368601@vcs2.savannah.gnu.org>
[not found] ` <20220412060205.8B446C01687@vcs2.savannah.gnu.org>
2022-04-12 6:15 ` master 2e9111813b: Add two classic Common Lisp macro-writing macros Sean Whitton
2022-04-12 7:14 ` Stefan Monnier
2022-04-12 15:57 ` Sean Whitton
2022-04-12 16:22 ` Stefan Monnier
2022-04-12 6:42 ` Po Lu
2022-04-12 18:43 ` Sean Whitton
2022-04-12 19:25 ` Eli Zaretskii
2022-04-13 5:48 ` Sean Whitton
2022-04-13 12:35 ` Eli Zaretskii
2022-04-13 19:46 ` Johann Klähn
2022-04-13 23:16 ` Sean Whitton
2022-04-13 3:58 ` Richard Stallman
2022-04-13 5:08 ` Sean Whitton
2022-04-14 2:56 ` Richard Stallman
2022-04-14 5:14 ` Sean Whitton
2022-04-14 12:06 ` [External] : " Drew Adams
2022-04-15 3:59 ` Richard Stallman
2022-04-15 6:14 ` Eli Zaretskii
2022-04-17 4:09 ` Richard Stallman
2022-04-17 1:57 ` Michael Heerdegen [this message]
2022-04-18 2:41 ` Richard Stallman
2022-04-18 5:18 ` Eli Zaretskii
2022-04-19 3:49 ` Richard Stallman
2022-04-12 8:46 ` Lars Ingebrigtsen
2022-04-12 15:52 ` Sean Whitton
2022-04-12 15:59 ` Lars Ingebrigtsen
2022-04-13 9:21 ` Philip Kaludercic
2022-04-13 15:14 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8v8mpye.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=rms@gnu.org \
--cc=spwhitton@spwhitton.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).