From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 68075@debbugs.gnu.org
Subject: bug#68075: 30.0.50; New special form `handler-bind`
Date: Mon, 01 Jan 2024 19:35:16 +0200 [thread overview]
Message-ID: <83h6jx0xez.fsf@gnu.org> (raw)
In-Reply-To: <jwv1qb16lxe.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 01 Jan 2024 11:55:43 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 68075@debbugs.gnu.org
> Date: Mon, 01 Jan 2024 11:55:43 -0500
>
> >> So, IIUC, reading that text makes you feel unsure, but you don't really
> >> know what you're unsure of?
> >
> > Oh, but I do: the two references to "dynamic", including one to
> > "dynamic binding" seem to indicate quite unequivocally that "dynamic
> > binding" vs "lexical binding" could be involved.
>
> Yes, it is involved: statically scoped vars are not affected, while
> dynamically scoped vars are affected, which is why the text says
> "dynamic".
Ah, so lexical binding _is_ relevant to this, in the sense that
lexically-bound variables are _not_ affected! Then please say that,
maybe in parentheses or as a footnote.
And please don't use "statically scoped", because we don't use this
terminology anywhere in the ELisp manual. We always say "lexical
scoping".
> Sadly, I still fail to grasp what kind of change to the wording could
> address the problem because I still don't really understand the problem.
> Maybe you could try to rewrite that bit in a way that you find more
> clear (or if there's still some part of the behavior over which you have
> doubts, then I'd be happily to try and explain it further).
I hope now it is more clear.
next prev parent reply other threads:[~2024-01-01 17:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 6:33 bug#68075: 30.0.50; New special form `handler-bind` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-28 8:03 ` Eli Zaretskii
2023-12-28 18:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-28 18:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-30 7:50 ` Eli Zaretskii
2023-12-28 18:25 ` Ihor Radchenko
2023-12-28 22:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-30 7:52 ` Eli Zaretskii
2023-12-31 19:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-31 19:36 ` Eli Zaretskii
2024-01-01 15:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-01 16:06 ` Eli Zaretskii
2024-01-01 16:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-01 17:35 ` Eli Zaretskii [this message]
2024-01-02 4:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-04 23:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-05 0:38 ` Stefan Kangas
2024-01-05 0:50 ` Stefan Kangas
2024-01-05 2:57 ` Stefan Monnier 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
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=83h6jx0xez.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68075@debbugs.gnu.org \
--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 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).