From: "Paul W. Rankin" via "Emacs development discussions." <emacs-devel@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: 'M-o' ('facemap-keymap') has now been removed until March 10th 2021
Date: Wed, 24 Mar 2021 09:08:21 +1000 [thread overview]
Message-ID: <4B2A00EB-8C04-4B9D-BA86-692D67207AFD@bydasein.com> (raw)
In-Reply-To: <22aaf0faddac64397c7d@heytings.org>
> 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.
next prev parent reply other threads:[~2021-03-23 23:08 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 21:38 'M-o' ('facemap-keymap') has now been removed until March 10th 2021 Paul W. Rankin via Emacs development discussions.
2021-03-23 22:07 ` Gregory Heytings
2021-03-23 23:08 ` Paul W. Rankin via Emacs development discussions. [this message]
2021-03-23 23:13 ` Gregory Heytings
2021-03-24 5:40 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 8:01 ` Gregory Heytings
2021-03-24 9:09 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 9:20 ` Gregory Heytings
2021-03-24 9:33 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 9:44 ` Gregory Heytings
2021-03-24 12:00 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 12:12 ` Gregory Heytings
2021-03-24 12:35 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 13:01 ` Gregory Heytings
2021-03-24 13:09 ` Stefan Monnier
2021-03-24 13:30 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 15:14 ` Stefan Monnier
2021-03-24 15:38 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 15:40 ` Stefan Monnier
2021-03-24 15:53 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 21:47 ` Stefan Monnier
2021-03-24 17:09 ` Eli Zaretskii
2021-03-24 21:58 ` Stefan Monnier
2021-03-25 6:15 ` Eli Zaretskii
2021-03-25 14:03 ` Stefan Monnier
2021-03-24 13:07 ` Stefan Monnier
2021-03-24 13:41 ` Paul W. Rankin via Emacs development discussions.
2021-03-24 13:53 ` Gregory Heytings
-- strict thread matches above, loose matches on Subject: below --
2021-02-10 18:40 Lars Ingebrigtsen
2021-02-10 19:14 ` Alan Mackenzie
2021-02-10 19:19 ` Lars Ingebrigtsen
2021-02-10 19:38 ` Lars Ingebrigtsen
2021-02-10 19:47 ` Alan Mackenzie
2021-02-11 13:34 ` Richard Stallman
2021-03-11 16:27 ` Lars Ingebrigtsen
2021-03-11 16:53 ` Eli Zaretskii
2021-03-11 17:02 ` Gregory Heytings
2021-03-11 17:29 ` Eli Zaretskii
2021-03-12 12:09 ` Filipp Gunbin
2021-03-12 12:46 ` Gregory Heytings
2021-03-11 17:37 ` Stefan Kangas
2021-03-11 18:25 ` Alfred M. Szmidt
2021-03-17 16:32 ` Sean Whitton
2021-03-18 3:43 ` Lars Ingebrigtsen
2021-03-18 4:35 ` Sean Whitton
2021-03-18 4:40 ` Lars Ingebrigtsen
2021-03-18 4:16 ` Lars Ingebrigtsen
2021-03-18 9:00 ` Eli Zaretskii
2021-03-18 10:27 ` Eli Zaretskii
2021-03-19 7:46 ` Lars Ingebrigtsen
2021-03-19 8:06 ` Eli Zaretskii
2021-03-19 9:35 ` Gregory Heytings
2021-03-19 12:01 ` Eli Zaretskii
2021-03-20 7:58 ` Lars Ingebrigtsen
2021-03-20 8:39 ` Andreas Schwab
2021-03-20 8:45 ` Lars Ingebrigtsen
2021-03-20 8:58 ` Gregory Heytings
2021-03-20 9:10 ` Eli Zaretskii
2021-03-18 13:28 ` Jean Louis
2021-03-18 14:45 ` Eli Zaretskii
2021-03-18 9:45 ` Alfred M. Szmidt
2021-03-18 13:25 ` Jean Louis
2021-03-18 23:03 ` Sean Whitton
2021-03-19 13:14 ` Gregory Heytings
2021-03-20 7:54 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B2A00EB-8C04-4B9D-BA86-692D67207AFD@bydasein.com \
--to=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=pwr@bydasein.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).