From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: master b72f885: Make dlet work like let, not let*
Date: Wed, 04 Aug 2021 14:40:16 +0300 [thread overview]
Message-ID: <83sfzpl9pb.fsf@gnu.org> (raw)
In-Reply-To: <878s1hucqi.fsf@web.de> (message from Michael Heerdegen on Wed, 04 Aug 2021 05:09:57 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Wed, 04 Aug 2021 05:09:57 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So what are your suggestions regarding this issue? Leave it as it is
> > now, go back to what we had before, something else?
>
> If you want another opinion: I find the name mildly confusing too. It
> has the potential that people write broken code (vs. we brake code
> because of this change now).
>
> And I think this is that kind of thing that tends to be discussed again
> and again.
This is not the issue which bothered me, not at all. What bothers me
is that we discuss the name of a macro that has been in our sources
for more than a year, and people and packages might depend on it.
Discussions about names should have been held a year ago, not now.
Now this is at most a minor issue that unfortunately slipped through
the cracks, and we shouldn't waste energy on arguing about it, same as
we do with typos or omissions in Git commit log messages: water under
the bridge.
> But it is definitely an extremely rarely used macro. FWIW, I can't
> remember the name for other reasons, I always search for something named
> "fluid-let" (Scheme) or "dynamical-let" (vs. "lexical-let" we had
> in the past) - but that may be only me.
If I learned something during my 30+ years of using and developing
Emacs it's that usage patterns differ wildly between people. What
looks rare and unimportant to me and you could be someone's bread and
butter.
next prev parent reply other threads:[~2021-08-04 11:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 16:10 master b72f885: Make dlet work like let, not let* Eli Zaretskii
2021-08-03 13:03 ` Mattias Engdegård
2021-08-03 13:33 ` Eli Zaretskii
2021-08-03 15:21 ` Mattias Engdegård
2021-08-03 15:58 ` Eli Zaretskii
2021-08-03 17:19 ` Stefan Monnier
2021-08-03 17:50 ` Eli Zaretskii
2021-08-03 18:50 ` Stefan Monnier
2021-08-04 11:27 ` Eli Zaretskii
2021-08-04 11:35 ` Lars Ingebrigtsen
2021-08-04 11:46 ` Mattias Engdegård
2021-08-04 12:16 ` Eli Zaretskii
2021-08-04 12:48 ` Mattias Engdegård
2021-08-04 12:15 ` Eli Zaretskii
2021-08-04 3:09 ` Michael Heerdegen
2021-08-04 11:40 ` Eli Zaretskii [this message]
2021-09-20 17:08 ` Jean Louis
2021-09-20 17:02 ` Jean Louis
2021-09-20 16:56 ` Jean Louis
2021-09-20 19:16 ` Tassilo Horn
2021-09-21 4:19 ` Jean Louis
2021-09-21 6:31 ` Tassilo Horn
2021-09-21 7:17 ` Jean Louis
2021-09-21 7:50 ` Tassilo Horn
2021-09-21 9:31 ` Jean Louis
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=83sfzpl9pb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).