GNU bug report logs -
#66117
30.0.50; `find-buffer-visiting' is slow when opening large number of buffers
Previous Next
Reported by: Ihor Radchenko <yantar92 <at> posteo.net>
Date: Wed, 20 Sep 2023 08:53:02 UTC
Severity: minor
Found in version 30.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #441 received at 66117 <at> debbugs.gnu.org (full text, mbox):
Ihor Radchenko [2024-01-01 18:02:30] wrote:
> Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:
>
>>> (defvar-local let-tests-buffer-local-var 'value)
>>> (with-temp-buffer
>>> (setq-local let-tests-buffer-local-var 'baz)
>>> (let ((let-tests-buffer-local-var 'bar))
>>> ;; This is failing.
>>> (should (eq 'bar (default-value 'let-tests-buffer-local-var)))
>>
>> C-h f default-value explains this:
>>
>> Return SYMBOL’s default value.
>> This is the value that is seen in buffers that do not have their own values
>> for this variable.
>
> Are you saying that `let' never changes `default-value' output?
> Unfortunately, no.
Indeed, see the doc that Eli quoted 10 posts "ago":
[...] ELisp manual, which describes the effect of
make-variable-buffer-local:
A peculiar wrinkle of this feature is that binding the variable
(with ‘let’ or other binding constructs) does not create
a buffer-local binding for it. Only setting the variable (with
‘set’ or ‘setq’), while the variable does not have a ‘let’-style
binding that was made in the current buffer, does so.
IOW, `let` changes the binding that is "current": if the variable is
buffer-local in the current buffer it changes that buffer-local value
and otherwise it changes the global value.
[ This for "automatically buffer-local variables". ]
Stefan
This bug report was last modified 1 year and 135 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.