From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Derived modes and mode hooks Date: Sat, 09 Mar 2013 10:56:52 -0500 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1362844626 3871 80.91.229.3 (9 Mar 2013 15:57:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Mar 2013 15:57:06 +0000 (UTC) Cc: emacs-devel To: Sebastian Wiesner Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 09 16:57:31 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UEM9J-0004A9-IP for ged-emacs-devel@m.gmane.org; Sat, 09 Mar 2013 16:57:29 +0100 Original-Received: from localhost ([::1]:35412 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UEM8x-0008NZ-Nm for ged-emacs-devel@m.gmane.org; Sat, 09 Mar 2013 10:57:07 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:59121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UEM8p-0008IP-9p for emacs-devel@gnu.org; Sat, 09 Mar 2013 10:57:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UEM8k-0000hW-1H for emacs-devel@gnu.org; Sat, 09 Mar 2013 10:56:59 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:60470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UEM8j-0000hQ-TL for emacs-devel@gnu.org; Sat, 09 Mar 2013 10:56:53 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFsoXZ8/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDiGGcGYFegxU X-IPAS-Result: Av4EABK/CFFsoXZ8/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDiGGcGYFegxU X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="3503224" Original-Received: from 108-161-118-124.dsl.teksavvy.com (HELO pastel.home) ([108.161.118.124]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 09 Mar 2013 10:56:51 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 83AA9678E8; Sat, 9 Mar 2013 10:56:52 -0500 (EST) In-Reply-To: (Sebastian Wiesner's message of "Sat, 9 Mar 2013 15:06:00 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:157666 Archived-At: > Is this right? If so, how can `body-of-foo-mode` forcibly overrule > settings made in `text-mode-hook`? It can't (well, if it really really wants to, it can add some code to its own foo-mode-hook which is run after text-mode-hook). A function added to a mode hook takes precedence, because it's presumably a user choice, whereas body-of-foo-mode is the choice of code's author. If the user doesn't want auto-fill-mode in foo-mode, she can add to foo-mode-hook to turn auto-fill-mode off, or she can change her text-mode-hook to test (derived-mode-p 'foo-mode) before enabling auto-fill-mode. Stefan