From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: gerd.moellmann@gmail.com, 65209@debbugs.gnu.org
Subject: bug#65209: 30.0.50; Unexpected behaviour of setq-local
Date: Sun, 13 Aug 2023 08:53:28 +0300 [thread overview]
Message-ID: <83o7jbcwtj.fsf@gnu.org> (raw)
In-Reply-To: <87r0o7r2z9.fsf@web.de> (message from Michael Heerdegen on Sun, 13 Aug 2023 06:16:42 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Gerd Möllmann <gerd.moellmann@gmail.com>,
> 65209@debbugs.gnu.org
> Date: Sun, 13 Aug 2023 06:16:42 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > > `setq' sets the buffer local binding, not the global value the `let'
> > > > binding refers to.
>
> > I guess this bug can be closed, then? Or is there anything left to
> > do?
>
> After thinking more about it:
>
> I could explain the behavior of Gerd's recipes using the manual, but it
> doesn't explain the state in my above example _after_ the `let' has
> been left.
>
> The manual has a *Warning* section about mixing `let', buffer-local
> variables, and changing the current buffer. But it doesn't explain what
> happens in a single buffer when you `let'-bind a (declared) variable,
> make it local inside the `let', and finish the `let'. Is the variable
> still buffer-local afterwards, or does `let' remove the
> buffer-localness? With other words, is leaving a `let' the same as a
> `setq' to the remembered value, or is it more?
>
> Do we answer that question somewhere? If not, I suggest to add that,
> maybe as an example before the *Warning* section.
I added Stefan to this discussion near its beginning, but you've
removed his address from the CC list. I've now re-added him back in
the hope that he can shed some light on the convoluted case you
describe.
next prev parent reply other threads:[~2023-08-13 5:53 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 [this message]
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
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=83o7jbcwtj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65209@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=michael_heerdegen@web.de \
--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).