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

[Stefan Monnier]

>> `*-change-functions` should not modify the buffer
> That's not what happened in the case described in that bug, AFAIR.

No, indeed.

>> 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.

If we have to run them some time between `before-c-f` and `after-c-f`,
then they should not modify the buffer, just like the
`*-change-functions` 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.

🙂


        Stefan