From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: org-mode and mode hooks. Date: Tue, 7 Jun 2005 20:36:45 -0500 (CDT) Message-ID: <200506080136.j581ajr21542@raven.dms.auburn.edu> References: <87y8a3mnz8.fsf@xs4all.nl> <200505290157.j4T1vus10117@raven.dms.auburn.edu> <200505292354.j4TNsTE13354@raven.dms.auburn.edu> <200505311544.j4VFijq17680@raven.dms.auburn.edu> <200506011911.j51JBR025269@raven.dms.auburn.edu> <87oeap231t.fsf-monnier+emacs@gnu.org> <200506012242.j51MgBj26277@raven.dms.auburn.edu> <87r7flpubg.fsf-monnier+emacs@gnu.org> <200506012349.j51NnUA26352@raven.dms.auburn.edu> <200506031505.j53F5IE04403@raven.dms.auburn.edu> <200506041517.j54FHgg09328@raven.dms.auburn.edu> <200506062328.j56NSnY18148@raven.dms.auburn.edu> <87wtp6jarp.fsf-monnier+emacs@gnu.org> <200506071908.j NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1118194652 4020 80.91.229.2 (8 Jun 2005 01:37:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 8 Jun 2005 01:37:32 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 08 03:37:28 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DfpV3-0006yl-9p for ged-emacs-devel@m.gmane.org; Wed, 08 Jun 2005 03:36:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dfpbf-0005po-Kf for ged-emacs-devel@m.gmane.org; Tue, 07 Jun 2005 21:43:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DfpbJ-0005ns-0a for emacs-devel@gnu.org; Tue, 07 Jun 2005 21:43:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DfpbG-0005lp-An for emacs-devel@gnu.org; Tue, 07 Jun 2005 21:43:22 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DfpbG-0005lB-4p for emacs-devel@gnu.org; Tue, 07 Jun 2005 21:43:22 -0400 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DfpZB-00054Q-Rq; Tue, 07 Jun 2005 21:41:14 -0400 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id j581bcCK000676; Tue, 7 Jun 2005 20:37:38 -0500 (CDT) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id j581ajr21542; Tue, 7 Jun 2005 20:36:45 -0500 (CDT) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: monnier@iro.umontreal.ca In-reply-to: <874qc9kerl.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 07 Jun 2005 18:10:05 -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:38295 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:38295 Stefan Monnier wrote: Could be, but your change does not try to fix it, instead it documents the part of the misbehavior we happen to know about, thus legitimizing the use, rather than discouraging i.t But your previous text, even when read as intended: whereas I meant it to mean: Use a non-@code{nil} @var{mode} argument only when you use @code{font-lock-add-keywords} or @code{font-lock-remove-keywords} in your @file{.emacs} file. legitimizes the use, since it says that it is OK to use it in your .emacs, and that is probably the main use. It does not tell what difference it makes if you use a nil or non-nil argument from your .emacs. > The misleading text in question made me lose a lot of time. In what way, specifically? Which hook did you try? It was completely impossible to figure out what a nil MODE arg was _trying_ to do. You could not look at the actual behavior, because before my patches the behavior with a nil MODE argument made no sense. If Font Lock was for some reason enabled for the wrong mode, it was impossible to correct reliably. The docs clearly seemed to suggest that a nil argument tried to enable the keywords for MODE only and not for derived modes, like a non-nil argument does, only without the mysterious "subtle implementation problems". As mention, I'd like to semi-obsolete it, so I'd rather not document it further: use at your own risk. As long as it is mentioned for possible use in .emacs, it is not semi-obsolete. Sincerely, Luc.