Re: 'M-o' ('facemap-keymap') has now been removed until March 10th 2021

[Paul W. Rankin]

> On 24 Mar 2021, at 8:07 am, Gregory Heytings <gregory@heytings.org> wrote:
> 
> 
>> 
>> Unless I'm fundamentally missing something, the new command font-lock-update 
>> only duplicates the functionality of existing command 
>> font-lock-fontify-buffer, and adds some confusion...
>> 
> 
> It does not duplicate the fonctionality, font-lock-fontify-buffer is bugged, 
> font-lock-update isn't (hopefully).  To see one of its bugs, open your .emacs 
> file, M-x font-lock-mode (which turns font-lock-mode off), M-x 
> font-lock-fontify-buffer.  Now change some characters: the fontification 
> remains.
> 
>> 
>> When font-lock-mode is active and font-lock-update is called with ARG, the 
>> command unfontifies the buffer and deactivates font-lock-mode. Wut? Makes no 
>> sense for a command called font-lock-update...
>> 
> 
> It allows you to toggle font-lock-mode correctly, which M-x font-lock-mode 
> can't do.  Try the following: emacs -Q, unless, M-., M-h, M-w, C-x b RET, M-x 
> text-mode, C-y, M-x font-lock-mode.

No bugs here. Both of these work as expected. I think the issue is you're 
confused about font-lock-mode and text properties. These are not the same 
thing. Font-lock-mode is just one way to add text properties to text, so may 
other functions. Deactivating font-lock-mode does not remove all text 
properties, only on text with the `(fontified . t)' property. This is why 
you're seeing what you're seeing.