From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: problem with mh-e and 2002-08-20 change to font-core.el Date: Fri, 30 Aug 2002 02:09:21 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: References: <200208260738.g7Q7c8S23362@localhost.localdomain> <200208262151.g7QLpN812743@wijiji.santafe.edu> <200208262209.g7QM9cx26500@rum.cs.yale.edu> <200208280653.g7S6r4p13393@wijiji.santafe.edu> <200208281355.g7SDtUl03773@rum.cs.yale.edu> <200208291525.g7TFPgG10906@rum.cs.yale.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1030687884 21448 127.0.0.1 (30 Aug 2002 06:11:24 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 30 Aug 2002 06:11:24 +0000 (UTC) Cc: monnier+gnu/emacs@rum.cs.yale.edu, y@mit.edu, mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17kf05-0005Zi-00 for ; Fri, 30 Aug 2002 08:11:21 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17kfWi-0003RI-00 for ; Fri, 30 Aug 2002 08:45:04 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17kf1U-0002NR-00; Fri, 30 Aug 2002 02:12:48 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17keyC-00020N-00 for emacs-devel@gnu.org; Fri, 30 Aug 2002 02:09:24 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17keyA-0001zx-00 for emacs-devel@gnu.org; Fri, 30 Aug 2002 02:09:23 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.10) id 17key9-0001zs-00 for emacs-devel@gnu.org; Fri, 30 Aug 2002 02:09:21 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.10) id 17key9-00086U-00; Fri, 30 Aug 2002 02:09:21 -0400 Original-To: monnier+gnu/emacs@rum.cs.yale.edu In-Reply-To: <200208291525.g7TFPgG10906@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:7143 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:7143 > font-lock-face properties go in mode-specific places. But do the properties belong to the text or to the mode. I am not sure that question makes real sense, but the font-lock-face property is not specific to any one mode. The right font-lock-face properties for one mode are wrong for some others. I have the impression that most of those font-lock-face properties are added together with the corresponding text and that they can't be recovered just from the text. I.e. erasing them might not be the right thing to do since it loses information. For Occur mode, this is correct. Info mode automatically applies the properties to the text. With the current code, changing from Occur mode to Fundamental mode and back to Occur mode would lose the font-lock-face properties. That is a bug. With the change you propose, changing from Occur mode to Fundamental mode and then to Info mode would leave you with font-lock-face properties left over from Occur mode. That would be a bug. Is there any way to make both cases work right? The "erase the font-lock-face property when changing-mode" hook you added is only added when you turn on font-lock-mode, so the font-lock-face property will stay if you don't turn on font-lock-mode before changing major-mode. Now I understand. Is there a method that fixes this too?