Re: (insert ?\n) spuriously calls before-change-functions twice. Help!

[Stefan Monnier]

>> Even if we fix the bug, there can be any number of reasons why the two
>> hooks may occasionally not be paired, .....
> Really?  I would have thought they should be rigorously paired, without
> any "recursive" invocations in-between (barring elisp code doing this
> deliberately).

There's combine-after-change-functions for one.  Or there's the case
where a signal is thrown in between the two.  Of course, there's also
the nesting case.

>> .... so your hooks should be robust against such situations.  IOW it's
>> best to try and avoid relying in the after-hook on info passed from the
>> before hook.
> Haven't we discussed this before at some time?  ;-)

You mean I should just have said "Told ya!"?


        Stefan