GNU bug report logs - #66117
30.0.50; `find-buffer-visiting' is slow when opening large number of buffers

Previous Next

Full log

View this message in rfc822 format

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: dmitry <at> gutov.dev, Eli Zaretskii <eliz <at> gnu.org>, mattias.engdegard <at> gmail.com, Stefan Monnier <monnier <at> iro.umontreal.ca>, 66117 <at> debbugs.gnu.org
Subject: bug#66117: 30.0.50; `find-buffer-visiting' is slow when opening large number of buffers
Date: Tue, 02 Jan 2024 13:07:47 +0100

Ihor Radchenko <yantar92 <at> posteo.net> writes:

> Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:
>
>>> In my example, SYMBOL does get its own value in the buffer, but
>>> `default-value' still returns 'default-value.
>>
>> I assume you mean the example from above? This one:
>
> Yes.
>
>>>>> (defvar-local yant/test 'default-value)
>>>>> (with-temp-buffer
>>>>>   (setq yant/test 'local-value)
>>>>>   (default-value 'yant/test)) ; => 'default-value
>>
>> If so, the "gets its own ... _but_ default-value still returns..." hints
>> at the misunderstanding, maybe. It should be something like "because it
>> gets its own..., default-value returns...".
>>
>> Maybe one could reformulate the doc string of default-value like 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.
>>
>> =>
>>
>>   Return SYMBOL’s default value.
>>   This is the value that would be seen in the buffer if it didn't have
>>   its own value.
>>
>> Although I find the original clearer...
>
> Both versions are actually clear for me. What was not clear for me is
> how the docstring explains my `let' example.

Sorry, I've lost track what the let example is. 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.