From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, 65209@debbugs.gnu.org,
monnier@iro.umontreal.ca
Subject: bug#65209: 30.0.50; Unexpected behaviour of setq-local
Date: Wed, 23 Aug 2023 05:47:18 +0200 [thread overview]
Message-ID: <871qfu4dyx.fsf@web.de> (raw)
In-Reply-To: <83msyjtkeo.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 22 Aug 2023 13:56:47 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> IOW, it is impossible for me to judge whether some text is good enough
> for the manual without seeing the proposed text. IME, some very
> complicated issues are better left unsaid, especially if they
> sufficiently rare and obscure, to avoid making the more common
> scenarios potentially less clear.
True, I know what you mean. OTOH, a good understanding of the underlying
language (Elisp) makes the number of things that seem confusing or
obscure smaller.
Ok - I'm not good at writing documentation. As a start, do you think
that it's possible to create a good addition to the manual out of this
stub?
| The following example demonstrates which binding is "seen" when
| let-binding and buffer-local variables are combined:
|
| (defvar var :default)
|
| (with-temp-buffer
| (let ((var :let-bound))
| var ; --> :let-bound
| (setq-local var :buffer-local)
| var ; --> :buffer-local
| (with-temp-buffer var)) ; --> :let-bound
| var ; --> :buffer-local
| (with-temp-buffer var)) ; --> :default
|
|
| A lexical variable always refers to its lexical binding even when
| a buffer-local variable of the same name exists:
|
| (let ((lvar :lexical))
| (setq-local lvar :local)
| lvar ; --> :lexical
| (symbol-value 'lvar)) ; --> :local
I would not suggest such an addition if I would not have missed that
kind of information in the manual. In some situations the above stuff
gets important, and let-binding variables that are made buffer-local is
daily business. Maybe this stuff is clear to people with a different
background - I don't know.
Michael.
next prev parent reply other threads:[~2023-08-23 3:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 13:50 bug#65209: 30.0.50; Unexpected behaviour of setq-local Gerd Möllmann
2023-08-10 14:00 ` Eli Zaretskii
2023-08-11 0:17 ` Michael Heerdegen
2023-08-11 4:56 ` Gerd Möllmann
2023-08-11 5:53 ` Michael Heerdegen
2023-08-11 8:17 ` Gerd Möllmann
2023-08-11 11:09 ` Eli Zaretskii
2023-08-11 11:34 ` Gerd Möllmann
2023-08-11 11:36 ` Eli Zaretskii
2023-08-13 4:16 ` Michael Heerdegen
2023-08-13 5:53 ` Eli Zaretskii
2023-08-11 14:58 ` Drew Adams
2023-08-13 16:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-13 19:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-14 3:24 ` Michael Heerdegen
2023-08-14 4:05 ` Gerd Möllmann
2023-08-18 23:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 4:43 ` Michael Heerdegen
2023-08-20 6:49 ` Eli Zaretskii
2023-08-22 3:09 ` Michael Heerdegen
2023-08-22 10:56 ` Eli Zaretskii
2023-08-23 3:47 ` Michael Heerdegen [this message]
2023-08-23 11:39 ` Eli Zaretskii
2023-08-23 12:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 1:06 ` Michael Heerdegen
2023-08-24 5:22 ` Eli Zaretskii
2023-08-26 2:09 ` Michael Heerdegen
2023-08-26 6:02 ` Eli Zaretskii
2023-08-26 14:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-27 4:19 ` Michael Heerdegen
2023-08-24 3:31 ` Michael Heerdegen
2023-08-24 5:35 ` Eli Zaretskii
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=871qfu4dyx.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=65209@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.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 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).