From db0b58da1d1e5724c783550103fcf5bb363bb713 Mon Sep 17 00:00:00 2001 From: Alan Mackenzie Date: Thu, 10 Nov 2016 21:22:05 +0000 Subject: [PATCH] Correct the statement about programming modes always running prog-mode-hook. doc/emacs/modes.texi (Major Modes): Amend the statement about programming modes running prog-mode-hook to say that it applies to many (not all) such modes, and specifying exactly which modes. --- doc/emacs/modes.texi | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/doc/emacs/modes.texi b/doc/emacs/modes.texi index c1564e9299b..63e31ab568c 100644 --- a/doc/emacs/modes.texi +++ b/doc/emacs/modes.texi @@ -113,10 +113,13 @@ hook}, a customizable list of Lisp functions to run each time the mode is enabled in a buffer. @xref{Hooks}, for more information about hooks. Each mode hook is named after its major mode, e.g., Fortran mode has @code{fortran-mode-hook}. Furthermore, all text-based major -modes run @code{text-mode-hook}, and all programming language modes -run @code{prog-mode-hook}, prior to running their own mode hooks. -Hook functions can look at the value of the variable @code{major-mode} -to see which mode is actually being entered. +modes run @code{text-mode-hook}, and many programming language modes +@footnote{More specifically, the modes which are ''derived'' from +@code{prog-mode} (@pxref{Derived Modes,,, elisp, The Emacs Lisp +Reference Manual}).} (including all those distributed with Emacs) run +@code{prog-mode-hook}, prior to running their own mode hooks. Hook +functions can look at the value of the variable @code{major-mode} to +see which mode is actually being entered. Mode hooks are commonly used to enable minor modes (@pxref{Minor Modes}). For example, you can put the following lines in your init -- 2.11.4.GIT