Tassilo Horn writes: > Arthur Miller writes: > >>> Out of curiosity, why do you have fboundp-checks for font-lock-ensure >>> in the code? That's always true, isn't it? >> >> I don't know. Since font-lock has all its stuff abstracted into buffer >> local function variables, I am not sure if I can count it is not nil? > > But it's no buffer-local variable, it's a function. If you have emacs > 25.1 upwards, you have `font-lock-ensure'. > >> If I can I would gladly remove the check. I appreciate advice, I am >> not so familiar with all the details of everything. > > I think that's a common check for 3rd-party packages which want to keep > supporting emacs 24. But since you are hacking emacs core, there's no > need for that unless the function/variable is only defined if some > configure option is given or some lib is available. But none of the > latter applies to font-lock.el. > Yes, I have tested now, it works fine. I did even som minor refactoring. Don't know if anyone else cares at all, anyway here is updated patch.