On 03/18/2015 05:08 AM, Alan Mackenzie wrote:
> On Mon, Mar 16, 2015 at 04:53:28PM -0700, Daniel Colascione wrote:
>> On 02/01/2015 01:22 PM, Alan Mackenzie wrote:
>>> branch: emacs-24
>>> commit d69e9f1c24f37f36af33b0468c5a4e100dbb09b6
>>> Author: Alan Mackenzie <acm@muc.de>
>>> Commit: Alan Mackenzie <acm@muc.de>
> 
>>>     CC Mode: Stop Font Lock forcing fontification from BOL.  Fixes debbugs#19669.
> 
>>>     cc-mode.el (c-font-lock-init): Setq font-lock-extend-region-functions to
>>>     nil.
> 
>> This change is driving me nuts.  Consider the following buffer, with @
>> representing point:
> 
>> void foo() {
>>   @
>> }
> 
>> If I type [f o r SPC], then depending on timing, I see only the "or", or
>> only the "r", fontified in font-lock-keyword-face. A moment later,
>> jit-lock kicks in and refontifies the entire chunk properly.
> 
> Sorry about this.
> 
>> Can we please extend the start of the region back to at least the last `}'?
> 
> This could be a tricky one to solve.  For the sake of your sanity, please
> consider applying the following temporary patch; it "solves" the current
> problem, but unfortunately leaves bug #19669's symptoms apparent again.

I've been doing the equivalent in a mode hook. I'm not sure that
reverting to the previous behavior is the right thing either.
Fundamentally, it just feels wrong that the solution to any
fontification correctness bug should be to fontify less.