GNU bug report logs - #78221
31.0.50; Improving *-change-functions notifications

Previous Next

Full log

Message #14 received at 78221 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: 78221 <at> debbugs.gnu.org, yantar92 <at> posteo.net, acm <at> muc.de,
 monnier <at> iro.umontreal.ca, joaotavora <at> gmail.com
Subject: Re: bug#78221: 31.0.50; Improving *-change-functions notifications
Date: Sat, 03 May 2025 17:45:22 +0300

> Date: Sat, 3 May 2025 14:13:40 +0000
> Cc: 78221 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
>   João Távora <joaotavora <at> gmail.com>,
>   Ihor Radchenko <yantar92 <at> posteo.net>, acm <at> muc.de
> From: Alan Mackenzie <acm <at> muc.de>
> 
> before/after-change-functions functions SHOULDN'T themselves make
> changes to the buffer text (apart from text properties).

That's not how nested notifications happen in most, if not all, the
cases.  They happen because a function that calls the before-change at
the beginning and an after-change at the end calls, as part of its
processing, some other function, which itself modifies buffer text or
the text properties, and thus emits its own "nested" notifications.

Previous Next

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