From: Michael Heerdegen <michael_heerdegen@web.de>
To: 65209@debbugs.gnu.org
Cc: gerd.moellmann@gmail.com, monnier@iro.umontreal.ca
Subject: bug#65209: 30.0.50; Unexpected behaviour of setq-local
Date: Mon, 14 Aug 2023 05:24:49 +0200 [thread overview]
Message-ID: <87msyu2tmm.fsf@web.de> (raw)
In-Reply-To: <jwvleeepvtu.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Sun, 13 Aug 2023 15:51:04 -0400")
Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
> The patch below seems to work (for some reason, I'm getting several
> errors in `make check` today, but they seems unaffected by this patch
> (i.e. I get the same errors in a vanilla build)).
Thanks that you looked closer. I've installed the patch locally and
will report back when I find any problem.
> +(defvar-local data-tests--bug65209 :default-value)
> +
> +(ert-deftest data-tests-make-local-bug65209 ()
> + (let (vli vlo vgi vgo)
> + (with-temp-buffer
> + (let ((data-tests--bug65209 :let-bound-value))
> + ;; While `setq' would not make the var buffer-local
> + ;; (because we'd be setq-ing the let-binding instead),
> + ;; `setq-local' definitely should.
> + (setq-local data-tests--bug65209 :buffer-local-value)
> + (setq vgi (with-temp-buffer data-tests--bug65209))
> + (setq vli data-tests--bug65209))
> + (setq vgo (with-temp-buffer data-tests--bug65209))
> + (setq vlo data-tests--bug65209))
> + (should (equal (list vli vlo vgi vgo)
> + '(:buffer-local-value :buffer-local-value
> + :let-bound-value :default-value)))))
> +
That would actually be a very good example for
(info "(elisp) Intro to Buffer-Local") if you replace vli, vlo, vgi, vgo
with non-abbreviating names.
Michael.
next prev parent reply other threads:[~2023-08-14 3:24 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 [this message]
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=87msyu2tmm.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=65209@debbugs.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).