Re: What to do when font-lock-flush + font-lock-ensure do less than font-lock-fontify-buffer?

[Clément Pit--Claudel]

On 02/22/2016 11:13 AM, Eli Zaretskii wrote:
>> From: Clément Pit--Claudel <address@hidden>
>> Date: Sun, 21 Feb 2016 23:55:04 -0500
>>
>> IIUC the proper way in Emacs 25 to signal changes that require a 
>> refontification to font-lock is to call font-lock-flush. This doesn't always 
>> do as much as font-lock-fontify-buffer does, though.
>>
>> In particular, when the font-lock-fontified variable is nil (which does 
>> happen, though I don't know why; I don't know what this variable is for), 
>> then calling font-lock-fontify buffer does refontify the whole buffer, but 
>> font-lock-flush and font-lock-ensure don't seem to do anything.
>>
>> What's the proper way to mark a buffer for refontification (and refontify 
>> the visible portion) immediately in 25?
> 
> I think what you describe _is_ the proper way.  Can you show a test
> case which demonstrates how calling font-lock-flush followed by
> font-lock-ensure fails to do the job?

In any case where font-lock-fontified is nil font-lock-fontify-buffer will 
properly refontify the whole buffer, but font-lock-flush and font-lock ensure 
will not do anything. I don't know what causes that variable to be nil in the 
first place, though.

Clément.

signature.asc
Description: OpenPGP digital signature