[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: `font-lock-extend-region-functions' vs. `font-lock-extend-after-chan
Re: `font-lock-extend-region-functions' vs. `font-lock-extend-after-change-region-function'
Wed, 29 Apr 2009 16:45:04 -0400
On Wed, Apr 29, 2009 at 4:26 PM, Stefan Monnier
>> Is this intended to be fixed? For example, the extending of the
>> font-lock region could be made a seperate step which
>> `jit-lock-fontify-now' has to run explicitly.
> Yes. This problem was introduced in Emacs-22 but at the time I decided
> it was better to "keep it that way for now" (the freeze was coming) and
> fix it for Emacs-23, but I never got around to do it.
> The way I imagine fixing it is by changing jit-lock-functions such that
> the functions on that hook (e.g. font-lock-fontify-region) would return
> the new boundaries they used (or nil if they kept the boundaries passed
> by jit-lock).
Would that degrade gracefully in the presence of old jit-lock-functions?