Subject: bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made

From: Eli Zaretskii <[email-masked]>
Date: Sat, 30 Mar 2024 19:47:38 +0300

> From: Stefan Monnier <[email-masked]>
> Cc: [email-masked],  [email-masked],  [email-masked]
> Date: Sat, 30 Mar 2024 11:38:24 -0400
> 
> > I still stand by my opinion: Org is relying on something it cannot
> > rely upon, not as long as a function that changes a buffer can be
> > called from another function which changes the same buffer.
> 
> `*-change-functions` should not modify the buffer

That's not what happened in the case described in that bug, AFAIR.
Simply a buffer change started, then, before it ended, another nested
change was started.

> so the only cases I can think of where "a function that changes a
> buffer can be called from another function which changes the same
> buffer" is when both of those functions are in our C code and we
> should have enough control to fix those cases.

You forget the various hooks, other than buffer modification hooks.

> Alan did convince me that we should treat them as bugs and that we
> should try and fix them.

He didn't convince me.