From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: org-mode and mode hooks. Date: Wed, 01 Jun 2005 13:22:43 -0400 Message-ID: References: <87y8a3mnz8.fsf@xs4all.nl> <87ll63weye.fsf-monnier+emacs@gnu.org> <200505252135.j4PLZvt26969@raven.dms.auburn.edu> <87hdgrufcl.fsf-monnier+emacs@gnu.org> <200505260359.j4Q3xbj28809@raven.dms.auburn.edu> <87is16rsid.fsf-monnier+emacs@gnu.org> <200505261501.j4QF17h00246@raven.dms.auburn.edu> <87psveq60w.fsf-monnier+emacs@gnu.org> <200505271717.j4RHHGD07067@raven.dms.auburn.edu> <200505290157.j4T1vus10117@raven.dms.auburn.edu> <200505292354.j4TNsTE13354@raven.dms.auburn.edu> <200505311544.j4VFijq17680@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1117647182 28601 80.91.229.2 (1 Jun 2005 17:33:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 1 Jun 2005 17:33:02 +0000 (UTC) Cc: emacs-devel@gnu.org, teirllm@dms.auburn.edu, mmaug@yahoo.com, Lute.Kamstra.lists@xs4all.nl, dominik@science.uva.nl Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 01 19:32:53 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DdX49-0004bw-Vq for ged-emacs-devel@m.gmane.org; Wed, 01 Jun 2005 19:31:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DdX9U-0005gP-I9 for ged-emacs-devel@m.gmane.org; Wed, 01 Jun 2005 13:37:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DdX4i-0003RE-R4 for emacs-devel@gnu.org; Wed, 01 Jun 2005 13:32:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DdX4d-0003MG-Ko for emacs-devel@gnu.org; Wed, 01 Jun 2005 13:32:11 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DdX4a-0003Hx-05 for emacs-devel@gnu.org; Wed, 01 Jun 2005 13:32:08 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DdWyc-0005Pi-FJ for emacs-devel@gnu.org; Wed, 01 Jun 2005 13:25:58 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1DdWvT-0001EB-Nd; Wed, 01 Jun 2005 13:22:45 -0400 Original-To: Stefan Monnier In-reply-to: (message from Stefan Monnier on Tue, 31 May 2005 15:08:48 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:38005 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:38005 > Suppose we make font-lock-add-keywords with nil for MODE > record its argument in some permanent buffer-local variable. > Then changing the major mode and reenabling font-lock > would use the same keywords previously added. Problem is that some of those keywords should be permanent and others shouldn't. E.g. it depends whether they correspond to a minor mode which is permanent or not. Maybe we should label each of these things by the name of the minor mode. That way, we could tell which of them to discard. Or we could give each one a flag saying whether to preserve it when changing the major mode. Would that solve the problem?