From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.devel Subject: Re: 'M-o' ('facemap-keymap') has now been removed until March 10th 2021 Date: Wed, 24 Mar 2021 12:12:03 +0000 Message-ID: <8786a8e8fa911a5c9ef3@heytings.org> References: <32A55BBD-1A3F-4EC4-817F-7C3408C22A65@bydasein.com> <22aaf0faddac64397c7d@heytings.org> <4B2A00EB-8C04-4B9D-BA86-692D67207AFD@bydasein.com> <22aaf0faddc2bf87fd3a@heytings.org> <0009872A-AD9D-4B08-B714-BFEDDAAF9125@bydasein.com> <8786a8e8faf45a989904@heytings.org> <8786a8e8faa6f278b198@heytings.org> <8786a8e8fac78b35b5e9@heytings.org> <286451D4-3958-4EA4-B87A-A78DCB684E5C@bydasein.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8467"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , emacs-devel@gnu.org To: "Paul W. Rankin" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Mar 24 13:13:12 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lP2Ns-00027W-5L for ged-emacs-devel@m.gmane-mx.org; Wed, 24 Mar 2021 13:13:12 +0100 Original-Received: from localhost ([::1]:56616 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lP2Nr-0002zO-05 for ged-emacs-devel@m.gmane-mx.org; Wed, 24 Mar 2021 08:13:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38680) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lP2Mr-0002YL-Do for emacs-devel@gnu.org; Wed, 24 Mar 2021 08:12:09 -0400 Original-Received: from heytings.org ([95.142.160.155]:43434) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lP2Mp-0002BU-BP for emacs-devel@gnu.org; Wed, 24 Mar 2021 08:12:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1616587923; bh=Xy3XQj2QhVGEnSpLv/OlHhHEvCSoxctJ8pOM6wkreGc=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=oVq4i8JhZySAZa6YXUqZv3SAky4FM1CmHt7TrZE7g4wqxNBnYPU23sc3jFhoer1WI 4lxKDIgB8bY1rMMbU+HN7GmO4x/9m+c+d9RC9TeK6H+qEMfVjGUbBJ8Awx3Tlqo+L/ 20PDB516+otgM9SyU1uvZqI5WbAeMkltmZ4kcR6HiMOZelfo3flZYpg5SQgBIDydsz x8Hg/hRcFNSNK92/n31NY1Q9dLZF8w2GmGbGrPocxgiDBfDckI/KuBpCr3FCob/8tV LUn3/fYFx5VM2iEv9OK8DIUa0ROy/nfcczCp2u2Bhv+rn0lhJ/rQ7rZPymhnEJITBL 1kKS3IB4gk/Eg== In-Reply-To: <286451D4-3958-4EA4-B87A-A78DCB684E5C@bydasein.com> Received-SPF: pass client-ip=95.142.160.155; envelope-from=gregory@heytings.org; helo=heytings.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:266949 Archived-At: >> Does it? AFAICS, font-lock-unfontify-region does not "remove _all_ >> text properties", it uses remove-list-of-text-properties, which >> "removes _some_ properties from text", namely those of font-lock-mode. > > Sure, you're right that it does not remove *all* text properties per se. > It removes, let's say, "all that it can" which is more than "all that is > intended". > Please provide a recipe to demonstrate when this actually matters. >> 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. > > This is again correct behaviour. When you yank the defun from an > emacs-lisp-mode buffer into a text-mode buffer, you're inserting text > with (most of) its text properties, except for the property `(fontified > . t)' because within the context of *this* buffer, the text properties > have not been applied with font-lock-mode and so this would be false and > prevent font-lock from doing its work. > This is not the problem here. The problem is that M-x font-lock-mode (last part of the recipe) is supposed to turn font-lock-mode off, yet the font-lock-mode fontification remains. > > I hope this clears things up for you. Unless there's any outside > objection I'm going to fix up the command in master to reflect as pasted > above. > I strongly object, there's no need to "fix" a working command to make it worse.