Re: Unbalanced change hooks (part 2)

[Stefan Monnier]

> If it is indeed the case, then a solution to the problem would be to
> check that before- and after-c-f are called alternately.  Any time
> after-c-f is called twice in a row, we could reverse the change just made
> (using the undo list), invoke before-c-f, redo the change, then let
> after-c-f continue to completion.  If necessary, we can temporarily

Sounds like piling up workarounds to make up for a mistake in the
underlying design.


        Stefan