Re: Unbalanced change hooks (part 2) [Documentation fix still remaining]

[Stefan Monnier]

>> The optimization is beside the point: not calling b-c-f in some corner
>> case breaks the entire model because a user such as syntax-ppss relies
>> on b-c-f to know when to flush its cache, so if you don't call it when
>> the buffer is modified, the cache ends up stale.
> I'm saying that flushing the entire cache in that case is not a
> problem, it's what needs to be done anyway.

The problem is that b-c-f is not called at all, so syntax-ppss doesn't
know that it should flush (any part of) its cache.
Calling b-c-f on point-min...point-max would be perfectly fine, indeed.
But currently b-c-f is not called at all.


        Stefan