GNU bug report logs - #34765
26.1; with-temp-buffer should not run buffer-list-update-hook

Previous Next

Full log

View this message in rfc822 format

From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 34765 <at> debbugs.gnu.org, rudalics <at> gmx.at, larsi <at> gnus.org, monnier <at> IRO.UMontreal.CA, alexanderm <at> web.de
Subject: bug#34765: 26.1; with-temp-buffer should not run buffer-list-update-hook
Date: Mon, 30 Nov 2020 20:34:55 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
>> Cc: Lars Ingebrigtsen <larsi <at> gnus.org>,  Eli Zaretskii <eliz <at> gnu.org>,
>>   34765 <at> debbugs.gnu.org,  alexanderm <at> web.de,  monnier <at> IRO.UMontreal.CA
>> Date: Mon, 30 Nov 2020 18:07:12 +0000
>> 
>> If I create a temporary buffer with the proposed
>> 
>>   (generate-new-buffer "foo" t)
>> 
>> then how do I later tell Emacs that this buffer's hooks should run?
>
> The assumption is that you don't want to.  Recall that the original
> idea was to turn the hooks off unconditionally based on the buffer's
> name.  The above is a less drastic measure: it allows the code which
> creates the buffer to request that regardless of the name.  But the
> original motivation, that there are buffers where we want to never run
> the hooks, is still valid.
>
>> In other words, can we be sure that the buffers we choose to create with
>> inhibit_buffer_hooks set will *never* need to later unset it?
>
> We didn't see examples of such buffers, so we pretend they don't
> exist.
>
>> Should we expose a getter or setter for this buffer member
>
> Not until someone comes up crying that this is needed, and presents a
> convincing use case, IMO.

WFM.  I'll finish up Martin's patch with some docs then.

Thanks,

-- 
Basil

Previous Next

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