6451
|
1 @c -*-texinfo-*-
|
|
2 @c This is part of the GNU Emacs Lisp Reference Manual.
|
27189
|
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999
|
|
4 @c Free Software Foundation, Inc.
|
6451
|
5 @c See the file elisp.texi for copying conditions.
|
|
6 @setfilename ../info/modes
|
|
7 @node Modes, Documentation, Keymaps, Top
|
|
8 @chapter Major and Minor Modes
|
|
9 @cindex mode
|
|
10
|
|
11 A @dfn{mode} is a set of definitions that customize Emacs and can be
|
|
12 turned on and off while you edit. There are two varieties of modes:
|
|
13 @dfn{major modes}, which are mutually exclusive and used for editing
|
|
14 particular kinds of text, and @dfn{minor modes}, which provide features
|
|
15 that users can enable individually.
|
|
16
|
|
17 This chapter describes how to write both major and minor modes, how to
|
|
18 indicate them in the mode line, and how they run hooks supplied by the
|
|
19 user. For related topics such as keymaps and syntax tables, see
|
|
20 @ref{Keymaps}, and @ref{Syntax Tables}.
|
|
21
|
|
22 @menu
|
|
23 * Major Modes:: Defining major modes.
|
|
24 * Minor Modes:: Defining minor modes.
|
|
25 * Mode Line Format:: Customizing the text that appears in the mode line.
|
21007
|
26 * Imenu:: How a mode can provide a menu
|
|
27 of definitions in the buffer.
|
|
28 * Font Lock Mode:: How modes can highlight text according to syntax.
|
6451
|
29 * Hooks:: How to use hooks; how to write code that provides hooks.
|
|
30 @end menu
|
|
31
|
|
32 @node Major Modes
|
|
33 @section Major Modes
|
|
34 @cindex major mode
|
|
35 @cindex Fundamental mode
|
|
36
|
|
37 Major modes specialize Emacs for editing particular kinds of text.
|
|
38 Each buffer has only one major mode at a time.
|
|
39
|
|
40 The least specialized major mode is called @dfn{Fundamental mode}.
|
|
41 This mode has no mode-specific definitions or variable settings, so each
|
|
42 Emacs command behaves in its default manner, and each option is in its
|
|
43 default state. All other major modes redefine various keys and options.
|
|
44 For example, Lisp Interaction mode provides special key bindings for
|
21682
|
45 @kbd{C-j} (@code{eval-print-last-sexp}), @key{TAB}
|
6451
|
46 (@code{lisp-indent-line}), and other keys.
|
|
47
|
|
48 When you need to write several editing commands to help you perform a
|
|
49 specialized editing task, creating a new major mode is usually a good
|
|
50 idea. In practice, writing a major mode is easy (in contrast to
|
|
51 writing a minor mode, which is often difficult).
|
|
52
|
|
53 If the new mode is similar to an old one, it is often unwise to modify
|
|
54 the old one to serve two purposes, since it may become harder to use and
|
|
55 maintain. Instead, copy and rename an existing major mode definition
|
|
56 and alter the copy---or define a @dfn{derived mode} (@pxref{Derived
|
|
57 Modes}). For example, Rmail Edit mode, which is in
|
25875
|
58 @file{emacs/lisp/mail/rmailedit.el}, is a major mode that is very similar to
|
|
59 Text mode except that it provides two additional commands. Its
|
|
60 definition is distinct from that of Text mode, but uses that of Text mode.
|
6451
|
61
|
28603
|
62 Even if the new mode is not an obvious derivative of any other mode,
|
39793
1d5b7d31671f
Recommend the use of define-derived-mode (and nil argument).
Stefan Monnier <monnier@iro.umontreal.ca>
diff
changeset
|
63 it is convenient to use @code{define-derived-mode} with a @code{nil}
|
1d5b7d31671f
Recommend the use of define-derived-mode (and nil argument).
Stefan Monnier <monnier@iro.umontreal.ca>
diff
changeset
|
64 parent argument, since it automatically enforces the most important
|
1d5b7d31671f
Recommend the use of define-derived-mode (and nil argument).
Stefan Monnier <monnier@iro.umontreal.ca>
diff
changeset
|
65 coding conventions for you.
|
28603
|
66
|
21682
|
67 Rmail Edit mode offers an example of changing the major mode
|
|
68 temporarily for a buffer, so it can be edited in a different way (with
|
22252
|
69 ordinary Emacs commands rather than Rmail commands). In such cases, the
|
25751
|
70 temporary major mode usually provides a command to switch back to the
|
21682
|
71 buffer's usual mode (Rmail mode, in this case). You might be tempted to
|
|
72 present the temporary redefinitions inside a recursive edit and restore
|
|
73 the usual ones when the user exits; but this is a bad idea because it
|
|
74 constrains the user's options when it is done in more than one buffer:
|
|
75 recursive edits must be exited most-recently-entered first. Using an
|
|
76 alternative major mode avoids this limitation. @xref{Recursive
|
6451
|
77 Editing}.
|
|
78
|
25751
|
79 The standard GNU Emacs Lisp library directory tree contains the code
|
|
80 for several major modes, in files such as @file{text-mode.el},
|
6451
|
81 @file{texinfo.el}, @file{lisp-mode.el}, @file{c-mode.el}, and
|
25875
|
82 @file{rmail.el}. They are found in various subdirectories of the
|
|
83 @file{lisp} directory. You can study these libraries to see how modes
|
|
84 are written. Text mode is perhaps the simplest major mode aside from
|
6451
|
85 Fundamental mode. Rmail mode is a complicated and specialized mode.
|
|
86
|
|
87 @menu
|
|
88 * Major Mode Conventions:: Coding conventions for keymaps, etc.
|
|
89 * Example Major Modes:: Text mode and Lisp modes.
|
|
90 * Auto Major Mode:: How Emacs chooses the major mode automatically.
|
|
91 * Mode Help:: Finding out how to use a mode.
|
|
92 * Derived Modes:: Defining a new major mode based on another major
|
|
93 mode.
|
|
94 @end menu
|
|
95
|
|
96 @node Major Mode Conventions
|
|
97 @subsection Major Mode Conventions
|
|
98
|
|
99 The code for existing major modes follows various coding conventions,
|
|
100 including conventions for local keymap and syntax table initialization,
|
|
101 global names, and hooks. Please follow these conventions when you
|
38200
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
102 define a new major mode.
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
103
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
104 This list of conventions is only partial, because each major mode
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
105 should aim for consistency in general with other Emacs major modes.
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
106 This makes Emacs as a whole more coherent. It is impossible to list
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
107 here all the possible points where this issue might come up; if the
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
108 Emacs developers point out an area where your major mode deviates from
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
109 the usual conventions, please make it compatible.
|
6451
|
110
|
|
111 @itemize @bullet
|
|
112 @item
|
|
113 Define a command whose name ends in @samp{-mode}, with no arguments,
|
|
114 that switches to the new mode in the current buffer. This command
|
21682
|
115 should set up the keymap, syntax table, and buffer-local variables in an
|
|
116 existing buffer, without changing the buffer's contents.
|
6451
|
117
|
|
118 @item
|
7253
|
119 Write a documentation string for this command that describes the
|
6451
|
120 special commands available in this mode. @kbd{C-h m}
|
|
121 (@code{describe-mode}) in your mode will display this string.
|
|
122
|
|
123 The documentation string may include the special documentation
|
|
124 substrings, @samp{\[@var{command}]}, @samp{\@{@var{keymap}@}}, and
|
24934
|
125 @samp{\<@var{keymap}>}, which enable the documentation to adapt
|
6451
|
126 automatically to the user's own key bindings. @xref{Keys in
|
|
127 Documentation}.
|
|
128
|
|
129 @item
|
|
130 The major mode command should start by calling
|
21682
|
131 @code{kill-all-local-variables}. This is what gets rid of the
|
|
132 buffer-local variables of the major mode previously in effect.
|
6451
|
133
|
|
134 @item
|
|
135 The major mode command should set the variable @code{major-mode} to the
|
|
136 major mode command symbol. This is how @code{describe-mode} discovers
|
|
137 which documentation to print.
|
|
138
|
|
139 @item
|
|
140 The major mode command should set the variable @code{mode-name} to the
|
21682
|
141 ``pretty'' name of the mode, as a string. This string appears in the
|
|
142 mode line.
|
6451
|
143
|
|
144 @item
|
|
145 @cindex functions in modes
|
|
146 Since all global names are in the same name space, all the global
|
|
147 variables, constants, and functions that are part of the mode should
|
|
148 have names that start with the major mode name (or with an abbreviation
|
17278
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
149 of it if the name is long). @xref{Coding Conventions}.
|
6451
|
150
|
|
151 @item
|
38200
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
152 In a major mode for editing some kind of structured text, such as a
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
153 programming language, indentation of text according to structure is
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
154 probably useful. So the mode should set @code{indent-line-function}
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
155 to a suitable function, and probably customize other variables
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
156 for indentation.
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
157
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
158 @item
|
6451
|
159 @cindex keymaps in modes
|
|
160 The major mode should usually have its own keymap, which is used as the
|
21682
|
161 local keymap in all buffers in that mode. The major mode command should
|
|
162 call @code{use-local-map} to install this local map. @xref{Active
|
|
163 Keymaps}, for more information.
|
6451
|
164
|
21682
|
165 This keymap should be stored permanently in a global variable named
|
6451
|
166 @code{@var{modename}-mode-map}. Normally the library that defines the
|
7253
|
167 mode sets this variable.
|
6451
|
168
|
12803
|
169 @xref{Tips for Defining}, for advice about how to write the code to set
|
|
170 up the mode's keymap variable.
|
|
171
|
6451
|
172 @item
|
17278
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
173 The key sequences bound in a major mode keymap should usually start with
|
21682
|
174 @kbd{C-c}, followed by a control character, a digit, or @kbd{@{},
|
17278
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
175 @kbd{@}}, @kbd{<}, @kbd{>}, @kbd{:} or @kbd{;}. The other punctuation
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
176 characters are reserved for minor modes, and ordinary letters are
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
177 reserved for users.
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
178
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
179 It is reasonable for a major mode to rebind a key sequence with a
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
180 standard meaning, if it implements a command that does ``the same job''
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
181 in a way that fits the major mode better. For example, a major mode for
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
182 editing a programming language might redefine @kbd{C-M-a} to ``move to
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
183 the beginning of a function'' in a way that works better for that
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
184 language.
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
185
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
186 Major modes such as Dired or Rmail that do not allow self-insertion of
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
187 text can reasonably redefine letters and other printing characters as
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
188 editing commands. Dired and Rmail both do this.
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
189
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
190 @item
|
38161
|
191 Major modes must not define @key{RET} to do anything other than insert
|
|
192 a newline. The command to insert a newline and then indent is
|
38200
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
193 @kbd{C-j}. Please keep this distinction uniform for all major modes.
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
194
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
195 @item
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
196 Major modes should not alter options that are primary a matter of user
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
197 preference, such as whether Auto-Fill mode is enabled. Leave this to
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
198 each user to decide. However, a major mode should customize other
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
199 variables so that Auto-Fill mode will work usefully @emph{if} the user
|
6c286c714f74
(Major Mode Conventions): Say not to change meaning of RET, and not to
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
200 decides to use it.
|
38161
|
201
|
|
202 @item
|
6451
|
203 @cindex syntax tables in modes
|
|
204 The mode may have its own syntax table or may share one with other
|
|
205 related modes. If it has its own syntax table, it should store this in
|
7253
|
206 a variable named @code{@var{modename}-mode-syntax-table}. @xref{Syntax
|
6451
|
207 Tables}.
|
|
208
|
|
209 @item
|
16432
|
210 If the mode handles a language that has a syntax for comments, it should
|
|
211 set the variables that define the comment syntax. @xref{Options for
|
|
212 Comments,, Options Controlling Comments, emacs, The GNU Emacs Manual}.
|
|
213
|
|
214 @item
|
6451
|
215 @cindex abbrev tables in modes
|
|
216 The mode may have its own abbrev table or may share one with other
|
|
217 related modes. If it has its own abbrev table, it should store this in
|
|
218 a variable named @code{@var{modename}-mode-abbrev-table}. @xref{Abbrev
|
|
219 Tables}.
|
|
220
|
|
221 @item
|
16432
|
222 The mode should specify how to do highlighting for Font Lock mode, by
|
|
223 setting up a buffer-local value for the variable
|
21682
|
224 @code{font-lock-defaults} (@pxref{Font Lock Mode}).
|
16432
|
225
|
|
226 @item
|
|
227 The mode should specify how Imenu should find the definitions or
|
|
228 sections of a buffer, by setting up a buffer-local value for the
|
|
229 variable @code{imenu-generic-expression} or
|
21682
|
230 @code{imenu-create-index-function} (@pxref{Imenu}).
|
16432
|
231
|
|
232 @item
|
21682
|
233 Use @code{defvar} or @code{defcustom} to set mode-related variables, so
|
|
234 that they are not reinitialized if they already have a value. (Such
|
|
235 reinitialization could discard customizations made by the user.)
|
7253
|
236
|
|
237 @item
|
6451
|
238 @cindex buffer-local variables in modes
|
|
239 To make a buffer-local binding for an Emacs customization variable, use
|
|
240 @code{make-local-variable} in the major mode command, not
|
|
241 @code{make-variable-buffer-local}. The latter function would make the
|
|
242 variable local to every buffer in which it is subsequently set, which
|
|
243 would affect buffers that do not use this mode. It is undesirable for a
|
|
244 mode to have such global effects. @xref{Buffer-Local Variables}.
|
|
245
|
36347
|
246 With rare exceptions, the only reasonable way to use
|
25875
|
247 @code{make-variable-buffer-local} in a Lisp package is for a variable
|
|
248 which is used only within that package. Using it on a variable used by
|
|
249 other packages would interfere with them.
|
6451
|
250
|
|
251 @item
|
|
252 @cindex mode hook
|
|
253 @cindex major mode hook
|
|
254 Each major mode should have a @dfn{mode hook} named
|
|
255 @code{@var{modename}-mode-hook}. The major mode command should run that
|
|
256 hook, with @code{run-hooks}, as the very last thing it
|
17278
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
257 does. @xref{Hooks}.
|
6451
|
258
|
|
259 @item
|
|
260 The major mode command may also run the hooks of some more basic modes.
|
|
261 For example, @code{indented-text-mode} runs @code{text-mode-hook} as
|
|
262 well as @code{indented-text-mode-hook}. It may run these other hooks
|
|
263 immediately before the mode's own hook (that is, after everything else),
|
|
264 or it may run them earlier.
|
|
265
|
|
266 @item
|
|
267 If something special should be done if the user switches a buffer from
|
21007
|
268 this mode to any other major mode, this mode can set up a buffer-local
|
21682
|
269 value for @code{change-major-mode-hook} (@pxref{Creating Buffer-Local}).
|
6451
|
270
|
|
271 @item
|
|
272 If this mode is appropriate only for specially-prepared text, then the
|
|
273 major mode command symbol should have a property named @code{mode-class}
|
|
274 with value @code{special}, put on as follows:
|
|
275
|
|
276 @cindex @code{mode-class} property
|
|
277 @cindex @code{special}
|
|
278 @example
|
|
279 (put 'funny-mode 'mode-class 'special)
|
|
280 @end example
|
|
281
|
|
282 @noindent
|
25751
|
283 This tells Emacs that new buffers created while the current buffer is in
|
6451
|
284 Funny mode should not inherit Funny mode. Modes such as Dired, Rmail,
|
|
285 and Buffer List use this feature.
|
|
286
|
|
287 @item
|
|
288 If you want to make the new mode the default for files with certain
|
|
289 recognizable names, add an element to @code{auto-mode-alist} to select
|
|
290 the mode for those file names. If you define the mode command to
|
|
291 autoload, you should add this element in the same file that calls
|
|
292 @code{autoload}. Otherwise, it is sufficient to add the element in the
|
|
293 file that contains the mode definition. @xref{Auto Major Mode}.
|
|
294
|
|
295 @item
|
|
296 In the documentation, you should provide a sample @code{autoload} form
|
|
297 and an example of how to add to @code{auto-mode-alist}, that users can
|
25875
|
298 include in their init files (@pxref{Init File}).
|
6451
|
299
|
|
300 @item
|
|
301 @cindex mode loading
|
7253
|
302 The top-level forms in the file defining the mode should be written so
|
6451
|
303 that they may be evaluated more than once without adverse consequences.
|
|
304 Even if you never load the file more than once, someone else will.
|
|
305 @end itemize
|
|
306
|
|
307 @node Example Major Modes
|
|
308 @subsection Major Mode Examples
|
|
309
|
|
310 Text mode is perhaps the simplest mode besides Fundamental mode.
|
|
311 Here are excerpts from @file{text-mode.el} that illustrate many of
|
|
312 the conventions listed above:
|
|
313
|
|
314 @smallexample
|
|
315 @group
|
|
316 ;; @r{Create mode-specific tables.}
|
|
317 (defvar text-mode-syntax-table nil
|
|
318 "Syntax table used while in text mode.")
|
|
319 @end group
|
|
320
|
|
321 @group
|
|
322 (if text-mode-syntax-table
|
|
323 () ; @r{Do not change the table if it is already set up.}
|
|
324 (setq text-mode-syntax-table (make-syntax-table))
|
|
325 (modify-syntax-entry ?\" ". " text-mode-syntax-table)
|
|
326 (modify-syntax-entry ?\\ ". " text-mode-syntax-table)
|
|
327 (modify-syntax-entry ?' "w " text-mode-syntax-table))
|
|
328 @end group
|
|
329
|
|
330 @group
|
|
331 (defvar text-mode-abbrev-table nil
|
|
332 "Abbrev table used while in text mode.")
|
|
333 (define-abbrev-table 'text-mode-abbrev-table ())
|
|
334 @end group
|
|
335
|
|
336 @group
|
25875
|
337 (defvar text-mode-map nil ; @r{Create a mode-specific keymap.}
|
|
338 "Keymap for Text mode.
|
|
339 Many other modes, such as Mail mode, Outline mode and Indented Text mode,
|
|
340 inherit all the commands defined in this map.")
|
6451
|
341
|
|
342 (if text-mode-map
|
|
343 () ; @r{Do not change the keymap if it is already set up.}
|
|
344 (setq text-mode-map (make-sparse-keymap))
|
25875
|
345 (define-key text-mode-map "\e\t" 'ispell-complete-word)
|
22138
|
346 (define-key text-mode-map "\t" 'indent-relative)
|
6451
|
347 (define-key text-mode-map "\es" 'center-line)
|
|
348 (define-key text-mode-map "\eS" 'center-paragraph))
|
|
349 @end group
|
|
350 @end smallexample
|
|
351
|
|
352 Here is the complete major mode function definition for Text mode:
|
|
353
|
|
354 @smallexample
|
|
355 @group
|
|
356 (defun text-mode ()
|
25950
|
357 "Major mode for editing text intended for humans to read...
|
6451
|
358 Special commands: \\@{text-mode-map@}
|
|
359 @end group
|
|
360 @group
|
|
361 Turning on text-mode runs the hook `text-mode-hook'."
|
|
362 (interactive)
|
|
363 (kill-all-local-variables)
|
21682
|
364 (use-local-map text-mode-map)
|
|
365 @end group
|
|
366 @group
|
|
367 (setq local-abbrev-table text-mode-abbrev-table)
|
|
368 (set-syntax-table text-mode-syntax-table)
|
6451
|
369 @end group
|
|
370 @group
|
21682
|
371 (make-local-variable 'paragraph-start)
|
|
372 (setq paragraph-start (concat "[ \t]*$\\|" page-delimiter))
|
|
373 (make-local-variable 'paragraph-separate)
|
|
374 (setq paragraph-separate paragraph-start)
|
25875
|
375 (make-local-variable 'indent-line-function)
|
|
376 (setq indent-line-function 'indent-relative-maybe)
|
21682
|
377 @end group
|
|
378 @group
|
|
379 (setq mode-name "Text")
|
|
380 (setq major-mode 'text-mode)
|
6451
|
381 (run-hooks 'text-mode-hook)) ; @r{Finally, this permits the user to}
|
|
382 ; @r{customize the mode with a hook.}
|
|
383 @end group
|
|
384 @end smallexample
|
|
385
|
|
386 @cindex @file{lisp-mode.el}
|
|
387 The three Lisp modes (Lisp mode, Emacs Lisp mode, and Lisp
|
|
388 Interaction mode) have more features than Text mode and the code is
|
|
389 correspondingly more complicated. Here are excerpts from
|
|
390 @file{lisp-mode.el} that illustrate how these modes are written.
|
|
391
|
|
392 @cindex syntax table example
|
|
393 @smallexample
|
|
394 @group
|
|
395 ;; @r{Create mode-specific table variables.}
|
|
396 (defvar lisp-mode-syntax-table nil "")
|
|
397 (defvar emacs-lisp-mode-syntax-table nil "")
|
|
398 (defvar lisp-mode-abbrev-table nil "")
|
|
399 @end group
|
|
400
|
|
401 @group
|
|
402 (if (not emacs-lisp-mode-syntax-table) ; @r{Do not change the table}
|
|
403 ; @r{if it is already set.}
|
|
404 (let ((i 0))
|
|
405 (setq emacs-lisp-mode-syntax-table (make-syntax-table))
|
|
406 @end group
|
|
407
|
|
408 @group
|
|
409 ;; @r{Set syntax of chars up to 0 to class of chars that are}
|
|
410 ;; @r{part of symbol names but not words.}
|
25751
|
411 ;; @r{(The number 0 is @code{48} in the @sc{ascii} character set.)}
|
6451
|
412 (while (< i ?0)
|
|
413 (modify-syntax-entry i "_ " emacs-lisp-mode-syntax-table)
|
|
414 (setq i (1+ i)))
|
|
415 @dots{}
|
|
416 @end group
|
|
417 @group
|
|
418 ;; @r{Set the syntax for other characters.}
|
|
419 (modify-syntax-entry ? " " emacs-lisp-mode-syntax-table)
|
|
420 (modify-syntax-entry ?\t " " emacs-lisp-mode-syntax-table)
|
|
421 @dots{}
|
|
422 @end group
|
|
423 @group
|
|
424 (modify-syntax-entry ?\( "() " emacs-lisp-mode-syntax-table)
|
|
425 (modify-syntax-entry ?\) ")( " emacs-lisp-mode-syntax-table)
|
|
426 @dots{}))
|
|
427 ;; @r{Create an abbrev table for lisp-mode.}
|
|
428 (define-abbrev-table 'lisp-mode-abbrev-table ())
|
|
429 @end group
|
|
430 @end smallexample
|
|
431
|
|
432 Much code is shared among the three Lisp modes. The following
|
|
433 function sets various variables; it is called by each of the major Lisp
|
|
434 mode functions:
|
|
435
|
|
436 @smallexample
|
|
437 @group
|
|
438 (defun lisp-mode-variables (lisp-syntax)
|
|
439 (cond (lisp-syntax
|
21682
|
440 (set-syntax-table lisp-mode-syntax-table)))
|
6451
|
441 (setq local-abbrev-table lisp-mode-abbrev-table)
|
22138
|
442 @dots{}
|
6451
|
443 @end group
|
|
444 @end smallexample
|
|
445
|
|
446 Functions such as @code{forward-paragraph} use the value of the
|
|
447 @code{paragraph-start} variable. Since Lisp code is different from
|
|
448 ordinary text, the @code{paragraph-start} variable needs to be set
|
|
449 specially to handle Lisp. Also, comments are indented in a special
|
|
450 fashion in Lisp and the Lisp modes need their own mode-specific
|
|
451 @code{comment-indent-function}. The code to set these variables is the
|
|
452 rest of @code{lisp-mode-variables}.
|
|
453
|
|
454 @smallexample
|
|
455 @group
|
|
456 (make-local-variable 'paragraph-start)
|
21682
|
457 (setq paragraph-start (concat page-delimiter "\\|$" ))
|
|
458 (make-local-variable 'paragraph-separate)
|
|
459 (setq paragraph-separate paragraph-start)
|
6451
|
460 @dots{}
|
|
461 @end group
|
|
462 @group
|
|
463 (make-local-variable 'comment-indent-function)
|
|
464 (setq comment-indent-function 'lisp-comment-indent))
|
25875
|
465 @dots{}
|
6451
|
466 @end group
|
|
467 @end smallexample
|
|
468
|
|
469 Each of the different Lisp modes has a slightly different keymap. For
|
21007
|
470 example, Lisp mode binds @kbd{C-c C-z} to @code{run-lisp}, but the other
|
6451
|
471 Lisp modes do not. However, all Lisp modes have some commands in
|
21682
|
472 common. The following code sets up the common commands:
|
6451
|
473
|
|
474 @smallexample
|
|
475 @group
|
21682
|
476 (defvar shared-lisp-mode-map ()
|
|
477 "Keymap for commands shared by all sorts of Lisp modes.")
|
|
478
|
|
479 (if shared-lisp-mode-map
|
|
480 ()
|
|
481 (setq shared-lisp-mode-map (make-sparse-keymap))
|
|
482 (define-key shared-lisp-mode-map "\e\C-q" 'indent-sexp)
|
|
483 (define-key shared-lisp-mode-map "\177"
|
|
484 'backward-delete-char-untabify))
|
6451
|
485 @end group
|
|
486 @end smallexample
|
|
487
|
21682
|
488 @noindent
|
|
489 And here is the code to set up the keymap for Lisp mode:
|
6451
|
490
|
|
491 @smallexample
|
|
492 @group
|
21682
|
493 (defvar lisp-mode-map ()
|
25950
|
494 "Keymap for ordinary Lisp mode...")
|
21682
|
495
|
|
496 (if lisp-mode-map
|
6451
|
497 ()
|
21682
|
498 (setq lisp-mode-map (make-sparse-keymap))
|
|
499 (set-keymap-parent lisp-mode-map shared-lisp-mode-map)
|
|
500 (define-key lisp-mode-map "\e\C-x" 'lisp-eval-defun)
|
|
501 (define-key lisp-mode-map "\C-c\C-z" 'run-lisp))
|
6451
|
502 @end group
|
|
503 @end smallexample
|
|
504
|
|
505 Finally, here is the complete major mode function definition for
|
24934
|
506 Lisp mode.
|
6451
|
507
|
|
508 @smallexample
|
|
509 @group
|
21682
|
510 (defun lisp-mode ()
|
|
511 "Major mode for editing Lisp code for Lisps other than GNU Emacs Lisp.
|
6451
|
512 Commands:
|
|
513 Delete converts tabs to spaces as it moves back.
|
|
514 Blank lines separate paragraphs. Semicolons start comments.
|
21682
|
515 \\@{lisp-mode-map@}
|
|
516 Note that `run-lisp' may be used either to start an inferior Lisp job
|
|
517 or to switch back to an existing one.
|
6451
|
518 @end group
|
21682
|
519
|
6451
|
520 @group
|
21682
|
521 Entry to this mode calls the value of `lisp-mode-hook'
|
|
522 if that value is non-nil."
|
6451
|
523 (interactive)
|
|
524 (kill-all-local-variables)
|
|
525 @end group
|
|
526 @group
|
21682
|
527 (use-local-map lisp-mode-map) ; @r{Select the mode's keymap.}
|
|
528 (setq major-mode 'lisp-mode) ; @r{This is how @code{describe-mode}}
|
6451
|
529 ; @r{finds out what to describe.}
|
21682
|
530 (setq mode-name "Lisp") ; @r{This goes into the mode line.}
|
|
531 (lisp-mode-variables t) ; @r{This defines various variables.}
|
|
532 @end group
|
|
533 @group
|
|
534 (setq imenu-case-fold-search t)
|
|
535 (set-syntax-table lisp-mode-syntax-table)
|
|
536 (run-hooks 'lisp-mode-hook)) ; @r{This permits the user to use a}
|
6451
|
537 ; @r{hook to customize the mode.}
|
|
538 @end group
|
|
539 @end smallexample
|
|
540
|
|
541 @node Auto Major Mode
|
|
542 @subsection How Emacs Chooses a Major Mode
|
|
543
|
|
544 Based on information in the file name or in the file itself, Emacs
|
|
545 automatically selects a major mode for the new buffer when a file is
|
21682
|
546 visited. It also processes local variables specified in the file text.
|
6451
|
547
|
|
548 @deffn Command fundamental-mode
|
|
549 Fundamental mode is a major mode that is not specialized for anything
|
|
550 in particular. Other major modes are defined in effect by comparison
|
|
551 with this one---their definitions say what to change, starting from
|
|
552 Fundamental mode. The @code{fundamental-mode} function does @emph{not}
|
|
553 run any hooks; you're not supposed to customize it. (If you want Emacs
|
|
554 to behave differently in Fundamental mode, change the @emph{global}
|
|
555 state of Emacs.)
|
|
556 @end deffn
|
|
557
|
|
558 @deffn Command normal-mode &optional find-file
|
21682
|
559 This function establishes the proper major mode and buffer-local variable
|
6451
|
560 bindings for the current buffer. First it calls @code{set-auto-mode},
|
|
561 then it runs @code{hack-local-variables} to parse, and bind or
|
21682
|
562 evaluate as appropriate, the file's local variables.
|
6451
|
563
|
21682
|
564 If the @var{find-file} argument to @code{normal-mode} is non-@code{nil},
|
|
565 @code{normal-mode} assumes that the @code{find-file} function is calling
|
|
566 it. In this case, it may process a local variables list at the end of
|
|
567 the file and in the @samp{-*-} line. The variable
|
|
568 @code{enable-local-variables} controls whether to do so. @xref{File
|
|
569 variables, , Local Variables in Files, emacs, The GNU Emacs Manual}, for
|
|
570 the syntax of the local variables section of a file.
|
6451
|
571
|
12098
|
572 If you run @code{normal-mode} interactively, the argument
|
6451
|
573 @var{find-file} is normally @code{nil}. In this case,
|
|
574 @code{normal-mode} unconditionally processes any local variables list.
|
|
575
|
|
576 @cindex file mode specification error
|
12098
|
577 @code{normal-mode} uses @code{condition-case} around the call to the
|
6451
|
578 major mode function, so errors are caught and reported as a @samp{File
|
|
579 mode specification error}, followed by the original error message.
|
|
580 @end deffn
|
|
581
|
|
582 @defun set-auto-mode
|
|
583 @cindex visited file mode
|
|
584 This function selects the major mode that is appropriate for the
|
|
585 current buffer. It may base its decision on the value of the @w{@samp{-*-}}
|
12888
|
586 line, on the visited file name (using @code{auto-mode-alist}), on the
|
|
587 @w{@samp{#!}} line (using @code{interpreter-mode-alist}), or on the
|
21682
|
588 file's local variables list. However, this function does not look for
|
6451
|
589 the @samp{mode:} local variable near the end of a file; the
|
|
590 @code{hack-local-variables} function does that. @xref{Choosing Modes, ,
|
|
591 How Major Modes are Chosen, emacs, The GNU Emacs Manual}.
|
|
592 @end defun
|
|
593
|
|
594 @defopt default-major-mode
|
21682
|
595 This variable holds the default major mode for new buffers. The
|
6451
|
596 standard value is @code{fundamental-mode}.
|
|
597
|
21682
|
598 If the value of @code{default-major-mode} is @code{nil}, Emacs uses
|
6451
|
599 the (previously) current buffer's major mode for the major mode of a new
|
21007
|
600 buffer. However, if that major mode symbol has a @code{mode-class}
|
6451
|
601 property with value @code{special}, then it is not used for new buffers;
|
|
602 Fundamental mode is used instead. The modes that have this property are
|
|
603 those such as Dired and Rmail that are useful only with text that has
|
|
604 been specially prepared.
|
|
605 @end defopt
|
|
606
|
12067
|
607 @defun set-buffer-major-mode buffer
|
|
608 This function sets the major mode of @var{buffer} to the value of
|
|
609 @code{default-major-mode}. If that variable is @code{nil}, it uses
|
|
610 the current buffer's major mode (if that is suitable).
|
|
611
|
|
612 The low-level primitives for creating buffers do not use this function,
|
12098
|
613 but medium-level commands such as @code{switch-to-buffer} and
|
|
614 @code{find-file-noselect} use it whenever they create buffers.
|
12067
|
615 @end defun
|
|
616
|
6451
|
617 @defvar initial-major-mode
|
|
618 @cindex @samp{*scratch*}
|
|
619 The value of this variable determines the major mode of the initial
|
|
620 @samp{*scratch*} buffer. The value should be a symbol that is a major
|
21007
|
621 mode command. The default value is @code{lisp-interaction-mode}.
|
6451
|
622 @end defvar
|
|
623
|
|
624 @defvar auto-mode-alist
|
|
625 This variable contains an association list of file name patterns
|
|
626 (regular expressions; @pxref{Regular Expressions}) and corresponding
|
21007
|
627 major mode commands. Usually, the file name patterns test for suffixes,
|
|
628 such as @samp{.el} and @samp{.c}, but this need not be the case. An
|
|
629 ordinary element of the alist looks like @code{(@var{regexp} .
|
6451
|
630 @var{mode-function})}.
|
|
631
|
|
632 For example,
|
|
633
|
|
634 @smallexample
|
|
635 @group
|
21682
|
636 (("\\`/tmp/fol/" . text-mode)
|
8505
|
637 ("\\.texinfo\\'" . texinfo-mode)
|
|
638 ("\\.texi\\'" . texinfo-mode)
|
6451
|
639 @end group
|
|
640 @group
|
8505
|
641 ("\\.el\\'" . emacs-lisp-mode)
|
|
642 ("\\.c\\'" . c-mode)
|
|
643 ("\\.h\\'" . c-mode)
|
6451
|
644 @dots{})
|
|
645 @end group
|
|
646 @end smallexample
|
|
647
|
|
648 When you visit a file whose expanded file name (@pxref{File Name
|
|
649 Expansion}) matches a @var{regexp}, @code{set-auto-mode} calls the
|
|
650 corresponding @var{mode-function}. This feature enables Emacs to select
|
|
651 the proper major mode for most files.
|
|
652
|
|
653 If an element of @code{auto-mode-alist} has the form @code{(@var{regexp}
|
|
654 @var{function} t)}, then after calling @var{function}, Emacs searches
|
|
655 @code{auto-mode-alist} again for a match against the portion of the file
|
21682
|
656 name that did not match before. This feature is useful for
|
|
657 uncompression packages: an entry of the form @code{("\\.gz\\'"
|
|
658 @var{function} t)} can uncompress the file and then put the uncompressed
|
|
659 file in the proper mode according to the name sans @samp{.gz}.
|
6451
|
660
|
|
661 Here is an example of how to prepend several pattern pairs to
|
|
662 @code{auto-mode-alist}. (You might use this sort of expression in your
|
25875
|
663 init file.)
|
6451
|
664
|
|
665 @smallexample
|
|
666 @group
|
|
667 (setq auto-mode-alist
|
|
668 (append
|
21007
|
669 ;; @r{File name (within directory) starts with a dot.}
|
8505
|
670 '(("/\\.[^/]*\\'" . fundamental-mode)
|
7253
|
671 ;; @r{File name has no dot.}
|
8505
|
672 ("[^\\./]*\\'" . fundamental-mode)
|
7253
|
673 ;; @r{File name ends in @samp{.C}.}
|
8505
|
674 ("\\.C\\'" . c++-mode))
|
6451
|
675 auto-mode-alist))
|
|
676 @end group
|
|
677 @end smallexample
|
|
678 @end defvar
|
|
679
|
|
680 @defvar interpreter-mode-alist
|
21007
|
681 This variable specifies major modes to use for scripts that specify a
|
24934
|
682 command interpreter in a @samp{#!} line. Its value is a list of
|
6451
|
683 elements of the form @code{(@var{interpreter} . @var{mode})}; for
|
|
684 example, @code{("perl" . perl-mode)} is one element present by default.
|
|
685 The element says to use mode @var{mode} if the file specifies
|
21007
|
686 an interpreter which matches @var{interpreter}. The value of
|
|
687 @var{interpreter} is actually a regular expression.
|
6451
|
688
|
7253
|
689 This variable is applicable only when the @code{auto-mode-alist} does
|
|
690 not indicate which major mode to use.
|
6451
|
691 @end defvar
|
|
692
|
|
693 @node Mode Help
|
|
694 @subsection Getting Help about a Major Mode
|
|
695 @cindex mode help
|
|
696 @cindex help for major mode
|
|
697 @cindex documentation for major mode
|
|
698
|
|
699 The @code{describe-mode} function is used to provide information
|
|
700 about major modes. It is normally called with @kbd{C-h m}. The
|
|
701 @code{describe-mode} function uses the value of @code{major-mode},
|
|
702 which is why every major mode function needs to set the
|
|
703 @code{major-mode} variable.
|
|
704
|
|
705 @deffn Command describe-mode
|
|
706 This function displays the documentation of the current major mode.
|
|
707
|
|
708 The @code{describe-mode} function calls the @code{documentation}
|
|
709 function using the value of @code{major-mode} as an argument. Thus, it
|
|
710 displays the documentation string of the major mode function.
|
|
711 (@xref{Accessing Documentation}.)
|
|
712 @end deffn
|
|
713
|
|
714 @defvar major-mode
|
|
715 This variable holds the symbol for the current buffer's major mode.
|
7253
|
716 This symbol should have a function definition that is the command to
|
6451
|
717 switch to that major mode. The @code{describe-mode} function uses the
|
7253
|
718 documentation string of the function as the documentation of the major
|
6451
|
719 mode.
|
|
720 @end defvar
|
|
721
|
|
722 @node Derived Modes
|
|
723 @subsection Defining Derived Modes
|
|
724
|
|
725 It's often useful to define a new major mode in terms of an existing
|
|
726 one. An easy way to do this is to use @code{define-derived-mode}.
|
|
727
|
7253
|
728 @defmac define-derived-mode variant parent name docstring body@dots{}
|
6451
|
729 This construct defines @var{variant} as a major mode command, using
|
7253
|
730 @var{name} as the string form of the mode name.
|
6451
|
731
|
7253
|
732 The new command @var{variant} is defined to call the function
|
|
733 @var{parent}, then override certain aspects of that parent mode:
|
6451
|
734
|
|
735 @itemize @bullet
|
|
736 @item
|
|
737 The new mode has its own keymap, named @code{@var{variant}-map}.
|
|
738 @code{define-derived-mode} initializes this map to inherit from
|
|
739 @code{@var{parent}-map}, if it is not already set.
|
|
740
|
|
741 @item
|
7253
|
742 The new mode has its own syntax table, kept in the variable
|
6451
|
743 @code{@var{variant}-syntax-table}.
|
|
744 @code{define-derived-mode} initializes this variable by copying
|
|
745 @code{@var{parent}-syntax-table}, if it is not already set.
|
|
746
|
|
747 @item
|
7253
|
748 The new mode has its own abbrev table, kept in the variable
|
6451
|
749 @code{@var{variant}-abbrev-table}.
|
|
750 @code{define-derived-mode} initializes this variable by copying
|
|
751 @code{@var{parent}-abbrev-table}, if it is not already set.
|
|
752
|
|
753 @item
|
|
754 The new mode has its own mode hook, @code{@var{variant}-hook},
|
|
755 which it runs in standard fashion as the very last thing that it does.
|
|
756 (The new mode also runs the mode hook of @var{parent} as part
|
|
757 of calling @var{parent}.)
|
|
758 @end itemize
|
|
759
|
|
760 In addition, you can specify how to override other aspects of
|
7253
|
761 @var{parent} with @var{body}. The command @var{variant}
|
6451
|
762 evaluates the forms in @var{body} after setting up all its usual
|
|
763 overrides, just before running @code{@var{variant}-hook}.
|
|
764
|
|
765 The argument @var{docstring} specifies the documentation string for the
|
|
766 new mode. If you omit @var{docstring}, @code{define-derived-mode}
|
|
767 generates a documentation string.
|
|
768
|
|
769 Here is a hypothetical example:
|
|
770
|
|
771 @example
|
|
772 (define-derived-mode hypertext-mode
|
|
773 text-mode "Hypertext"
|
|
774 "Major mode for hypertext.
|
|
775 \\@{hypertext-mode-map@}"
|
|
776 (setq case-fold-search nil))
|
|
777
|
|
778 (define-key hypertext-mode-map
|
|
779 [down-mouse-3] 'do-hyper-link)
|
|
780 @end example
|
|
781 @end defmac
|
|
782
|
|
783 @node Minor Modes
|
|
784 @section Minor Modes
|
|
785 @cindex minor mode
|
|
786
|
|
787 A @dfn{minor mode} provides features that users may enable or disable
|
|
788 independently of the choice of major mode. Minor modes can be enabled
|
|
789 individually or in combination. Minor modes would be better named
|
21682
|
790 ``generally available, optional feature modes,'' except that such a name
|
|
791 would be unwieldy.
|
6451
|
792
|
25751
|
793 A minor mode is not usually meant as a variation of a single major mode.
|
|
794 Usually they are general and can apply to many major modes. For
|
21682
|
795 example, Auto Fill mode works with any major mode that permits text
|
6451
|
796 insertion. To be general, a minor mode must be effectively independent
|
|
797 of the things major modes do.
|
|
798
|
|
799 A minor mode is often much more difficult to implement than a major
|
|
800 mode. One reason is that you should be able to activate and deactivate
|
7253
|
801 minor modes in any order. A minor mode should be able to have its
|
|
802 desired effect regardless of the major mode and regardless of the other
|
|
803 minor modes in effect.
|
6451
|
804
|
|
805 Often the biggest problem in implementing a minor mode is finding a
|
|
806 way to insert the necessary hook into the rest of Emacs. Minor mode
|
12098
|
807 keymaps make this easier than it used to be.
|
6451
|
808
|
|
809 @menu
|
|
810 * Minor Mode Conventions:: Tips for writing a minor mode.
|
|
811 * Keymaps and Minor Modes:: How a minor mode can have its own keymap.
|
26696
|
812 * Defining Minor Modes:: A convenient facility for defining minor modes.
|
6451
|
813 @end menu
|
|
814
|
|
815 @node Minor Mode Conventions
|
|
816 @subsection Conventions for Writing Minor Modes
|
|
817 @cindex minor mode conventions
|
|
818 @cindex conventions for writing minor modes
|
|
819
|
|
820 There are conventions for writing minor modes just as there are for
|
|
821 major modes. Several of the major mode conventions apply to minor
|
|
822 modes as well: those regarding the name of the mode initialization
|
|
823 function, the names of global symbols, and the use of keymaps and
|
|
824 other tables.
|
|
825
|
|
826 In addition, there are several conventions that are specific to
|
|
827 minor modes.
|
|
828
|
|
829 @itemize @bullet
|
|
830 @item
|
|
831 @cindex mode variable
|
21682
|
832 Make a variable whose name ends in @samp{-mode} to control the minor
|
|
833 mode. We call this the @dfn{mode variable}. The minor mode command
|
|
834 should set this variable (@code{nil} to disable; anything else to
|
22252
|
835 enable).
|
21682
|
836
|
25751
|
837 If possible, implement the mode so that setting the variable
|
21682
|
838 automatically enables or disables the mode. Then the minor mode command
|
22252
|
839 does not need to do anything except set the variable.
|
6451
|
840
|
|
841 This variable is used in conjunction with the @code{minor-mode-alist} to
|
|
842 display the minor mode name in the mode line. It can also enable
|
|
843 or disable a minor mode keymap. Individual commands or hooks can also
|
|
844 check the variable's value.
|
|
845
|
|
846 If you want the minor mode to be enabled separately in each buffer,
|
|
847 make the variable buffer-local.
|
|
848
|
|
849 @item
|
|
850 Define a command whose name is the same as the mode variable.
|
|
851 Its job is to enable and disable the mode by setting the variable.
|
|
852
|
|
853 The command should accept one optional argument. If the argument is
|
|
854 @code{nil}, it should toggle the mode (turn it on if it is off, and off
|
|
855 if it is on). Otherwise, it should turn the mode on if the argument is
|
|
856 a positive integer, a symbol other than @code{nil} or @code{-}, or a
|
|
857 list whose @sc{car} is such an integer or symbol; it should turn the
|
|
858 mode off otherwise.
|
|
859
|
12098
|
860 Here is an example taken from the definition of @code{transient-mark-mode}.
|
|
861 It shows the use of @code{transient-mark-mode} as a variable that enables or
|
7253
|
862 disables the mode's behavior, and also shows the proper way to toggle,
|
|
863 enable or disable the minor mode based on the raw prefix argument value.
|
6451
|
864
|
|
865 @smallexample
|
|
866 @group
|
12098
|
867 (setq transient-mark-mode
|
|
868 (if (null arg) (not transient-mark-mode)
|
6451
|
869 (> (prefix-numeric-value arg) 0)))
|
|
870 @end group
|
|
871 @end smallexample
|
|
872
|
|
873 @item
|
|
874 Add an element to @code{minor-mode-alist} for each minor mode
|
21682
|
875 (@pxref{Mode Line Variables}), if you want to indicate the minor mode in
|
|
876 the mode line. This element should be a list of the following form:
|
6451
|
877
|
|
878 @smallexample
|
|
879 (@var{mode-variable} @var{string})
|
|
880 @end smallexample
|
|
881
|
7253
|
882 Here @var{mode-variable} is the variable that controls enabling of the
|
6451
|
883 minor mode, and @var{string} is a short string, starting with a space,
|
|
884 to represent the mode in the mode line. These strings must be short so
|
|
885 that there is room for several of them at once.
|
|
886
|
|
887 When you add an element to @code{minor-mode-alist}, use @code{assq} to
|
|
888 check for an existing element, to avoid duplication. For example:
|
|
889
|
|
890 @smallexample
|
|
891 @group
|
25875
|
892 (unless (assq 'leif-mode minor-mode-alist)
|
|
893 (setq minor-mode-alist
|
|
894 (cons '(leif-mode " Leif") minor-mode-alist)))
|
|
895 @end group
|
|
896 @end smallexample
|
|
897
|
|
898 @noindent
|
|
899 or like this, using @code{add-to-list} (@pxref{Setting Variables}):
|
|
900
|
|
901 @smallexample
|
|
902 @group
|
|
903 (add-to-list 'minor-mode-alist '(leif-mode " Leif"))
|
6451
|
904 @end group
|
|
905 @end smallexample
|
|
906 @end itemize
|
|
907
|
25751
|
908 Global minor modes distributed with Emacs should if possible support
|
|
909 enabling and disabling via Custom (@pxref{Customization}). To do this,
|
|
910 the first step is to define the mode variable with @code{defcustom}, and
|
|
911 specify @code{:type boolean}.
|
|
912
|
|
913 If just setting the variable is not sufficient to enable the mode, you
|
|
914 should also specify a @code{:set} method which enables the mode by
|
|
915 invoke the mode command. Note in the variable's documentation string that
|
|
916 setting the variable other than via Custom may not take effect.
|
|
917
|
|
918 Also mark the definition with an autoload cookie (@pxref{Autoload}),
|
|
919 and specify a @code{:require} so that customizing the variable will load
|
|
920 the library that defines the mode. This will copy suitable definitions
|
|
921 into @file{loaddefs.el} so that users can use @code{customize-option} to
|
|
922 enable the mode. For example:
|
|
923
|
|
924 @smallexample
|
|
925 @group
|
|
926
|
|
927 ;;;###autoload
|
|
928 (defcustom msb-mode nil
|
|
929 "Toggle msb-mode.
|
|
930 Setting this variable directly does not take effect;
|
|
931 use either \\[customize] or the function `msb-mode'."
|
|
932 :set (lambda (symbol value)
|
|
933 (msb-mode (or value 0)))
|
|
934 :initialize 'custom-initialize-default
|
|
935 :version "20.4"
|
|
936 :type 'boolean
|
|
937 :group 'msb
|
|
938 :require 'msb)
|
|
939 @end group
|
|
940 @end smallexample
|
|
941
|
6451
|
942 @node Keymaps and Minor Modes
|
|
943 @subsection Keymaps and Minor Modes
|
|
944
|
12098
|
945 Each minor mode can have its own keymap, which is active when the mode
|
|
946 is enabled. To set up a keymap for a minor mode, add an element to the
|
|
947 alist @code{minor-mode-map-alist}. @xref{Active Keymaps}.
|
6451
|
948
|
|
949 @cindex @code{self-insert-command}, minor modes
|
21007
|
950 One use of minor mode keymaps is to modify the behavior of certain
|
6451
|
951 self-inserting characters so that they do something else as well as
|
|
952 self-insert. In general, this is the only way to do that, since the
|
|
953 facilities for customizing @code{self-insert-command} are limited to
|
|
954 special cases (designed for abbrevs and Auto Fill mode). (Do not try
|
|
955 substituting your own definition of @code{self-insert-command} for the
|
|
956 standard one. The editor command loop handles this function specially.)
|
|
957
|
17278
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
958 The key sequences bound in a minor mode should consist of @kbd{C-c}
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
959 followed by a punctuation character @emph{other than} @kbd{@{},
|
25751
|
960 @kbd{@}}, @kbd{<}, @kbd{>}, @kbd{:}, and @kbd{;}. (Those few punctuation
|
17278
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
961 characters are reserved for major modes.)
|
8ed8412c1ce7
Document key binding conventions for major modes and minor modes.
Richard M. Stallman <rms@gnu.org>
diff
changeset
|
962
|
26696
|
963 @node Defining Minor Modes
|
|
964 @subsection Defining Minor Modes
|
21007
|
965
|
26696
|
966 The macro @code{define-minor-mode} offers a convenient way of
|
|
967 implementing a mode in one self-contained definition. It supports only
|
25751
|
968 buffer-local minor modes, not global ones.
|
21007
|
969
|
26696
|
970 @defmac define-minor-mode mode doc &optional init-value mode-indicator keymap body...
|
|
971 @tindex define-minor-mode
|
21007
|
972 This macro defines a new minor mode whose name is @var{mode} (a symbol).
|
26696
|
973 It defines a command named @var{mode} to toggle the minor
|
|
974 mode, with @var{doc} as its documentation string. It also defines a
|
|
975 variable named @var{mode}, which is set to @code{t} or @code{nil} by
|
|
976 enabling or disabling the mode. The variable is initialized to
|
|
977 @var{init-value}.
|
21007
|
978
|
26696
|
979 The command named @var{mode} finishes by executing the @var{body} forms,
|
|
980 if any, after it has performed the standard actions such as setting
|
|
981 the variable named @var{mode}.
|
21007
|
982
|
|
983 The string @var{mode-indicator} says what to display in the mode line
|
|
984 when the mode is enabled; if it is @code{nil}, the mode is not displayed
|
|
985 in the mode line.
|
|
986
|
|
987 The optional argument @var{keymap} specifies the keymap for the minor mode.
|
|
988 It can be a variable name, whose value is the keymap, or it can be an alist
|
|
989 specifying bindings in this form:
|
|
990
|
|
991 @example
|
|
992 (@var{key-sequence} . @var{definition})
|
|
993 @end example
|
|
994 @end defmac
|
|
995
|
26696
|
996 Here is an example of using @code{define-minor-mode}:
|
21007
|
997
|
|
998 @smallexample
|
26696
|
999 (define-minor-mode hungry-mode
|
21682
|
1000 "Toggle Hungry mode.
|
21007
|
1001 With no argument, this command toggles the mode.
|
|
1002 Non-null prefix argument turns on the mode.
|
|
1003 Null prefix argument turns off the mode.
|
|
1004
|
|
1005 When Hungry mode is enabled, the control delete key
|
|
1006 gobbles all preceding whitespace except the last.
|
|
1007 See the command \\[hungry-electric-delete]."
|
|
1008 ;; The initial value.
|
|
1009 nil
|
|
1010 ;; The indicator for the mode line.
|
|
1011 " Hungry"
|
|
1012 ;; The minor mode bindings.
|
|
1013 '(("\C-\^?" . hungry-electric-delete)
|
|
1014 ("\C-\M-\^?"
|
|
1015 . (lambda ()
|
|
1016 (interactive)
|
|
1017 (hungry-electric-delete t)))))
|
|
1018 @end smallexample
|
|
1019
|
|
1020 @noindent
|
|
1021 This defines a minor mode named ``Hungry mode'', a command named
|
|
1022 @code{hungry-mode} to toggle it, a variable named @code{hungry-mode}
|
|
1023 which indicates whether the mode is enabled, and a variable named
|
|
1024 @code{hungry-mode-map} which holds the keymap that is active when the
|
|
1025 mode is enabled. It initializes the keymap with key bindings for
|
|
1026 @kbd{C-@key{DEL}} and @kbd{C-M-@key{DEL}}.
|
|
1027
|
26696
|
1028
|
|
1029 @findex easy-mmode-define-minor-mode
|
|
1030 The name @code{easy-mmode-define-minor-mode} is an alias
|
|
1031 for this macro.
|
|
1032
|
6451
|
1033 @node Mode Line Format
|
|
1034 @section Mode Line Format
|
|
1035 @cindex mode line
|
|
1036
|
25751
|
1037 Each Emacs window (aside from minibuffer windows) typically has a mode
|
|
1038 line at the bottom, which displays status information about the buffer
|
|
1039 displayed in the window. The mode line contains information about the
|
|
1040 buffer, such as its name, associated file, depth of recursive editing,
|
|
1041 and major and minor modes. A window can also have a @dfn{header
|
|
1042 line}, which is much like the mode line but appears at the top of the
|
|
1043 window (starting in Emacs 21).
|
6451
|
1044
|
25751
|
1045 This section describes how to control the contents of the mode line
|
|
1046 and header line. We include it in this chapter because much of the
|
6451
|
1047 information displayed in the mode line relates to the enabled major and
|
|
1048 minor modes.
|
|
1049
|
|
1050 @code{mode-line-format} is a buffer-local variable that holds a
|
|
1051 template used to display the mode line of the current buffer. All
|
25751
|
1052 windows for the same buffer use the same @code{mode-line-format}, so
|
|
1053 their mode lines appear the same---except for scrolling percentages, and
|
|
1054 line and column numbers, since those depend on point and on how the
|
|
1055 window is scrolled. @code{header-line-format} is used likewise for
|
|
1056 header lines.
|
6451
|
1057
|
25751
|
1058 The mode line and header line of a window are normally updated
|
|
1059 whenever a different buffer is shown in the window, or when the buffer's
|
|
1060 modified-status changes from @code{nil} to @code{t} or vice-versa. If
|
|
1061 you modify any of the variables referenced by @code{mode-line-format}
|
|
1062 (@pxref{Mode Line Variables}), or any other variables and data
|
|
1063 structures that affect how text is displayed (@pxref{Display}), you may
|
|
1064 want to force an update of the mode line so as to display the new
|
|
1065 information or display it in the new way.
|
6451
|
1066
|
|
1067 @c Emacs 19 feature
|
|
1068 @defun force-mode-line-update
|
25751
|
1069 Force redisplay of the current buffer's mode line and header line.
|
6451
|
1070 @end defun
|
|
1071
|
|
1072 The mode line is usually displayed in inverse video; see
|
|
1073 @code{mode-line-inverse-video} in @ref{Inverse Video}.
|
|
1074
|
|
1075 @menu
|
|
1076 * Mode Line Data:: The data structure that controls the mode line.
|
|
1077 * Mode Line Variables:: Variables used in that data structure.
|
|
1078 * %-Constructs:: Putting information into a mode line.
|
25751
|
1079 * Properties in Mode:: Using text properties in the mode line.
|
|
1080 * Header Lines:: Like a mode line, but at the top.
|
6451
|
1081 @end menu
|
|
1082
|
|
1083 @node Mode Line Data
|
|
1084 @subsection The Data Structure of the Mode Line
|
|
1085 @cindex mode line construct
|
|
1086
|
|
1087 The mode line contents are controlled by a data structure of lists,
|
25875
|
1088 strings, symbols, and numbers kept in buffer-local variables. The data
|
|
1089 structure is called a @dfn{mode line construct}, and it is built in
|
|
1090 recursive fashion out of simpler mode line constructs. The same data
|
|
1091 structure is used for constructing frame titles (@pxref{Frame Titles})
|
|
1092 and header lines (@pxref{Header Lines}).
|
6451
|
1093
|
|
1094 @defvar mode-line-format
|
|
1095 The value of this variable is a mode line construct with overall
|
|
1096 responsibility for the mode line format. The value of this variable
|
|
1097 controls which other variables are used to form the mode line text, and
|
|
1098 where they appear.
|
25751
|
1099
|
|
1100 If you set this variable to @code{nil} in a buffer, that buffer does not
|
|
1101 have a mode line. (This feature was added in Emacs 21.)
|
6451
|
1102 @end defvar
|
|
1103
|
|
1104 A mode line construct may be as simple as a fixed string of text, but
|
|
1105 it usually specifies how to use other variables to construct the text.
|
|
1106 Many of these variables are themselves defined to have mode line
|
|
1107 constructs as their values.
|
|
1108
|
|
1109 The default value of @code{mode-line-format} incorporates the values
|
|
1110 of variables such as @code{mode-name} and @code{minor-mode-alist}.
|
21007
|
1111 Because of this, very few modes need to alter @code{mode-line-format}
|
|
1112 itself. For most purposes, it is sufficient to alter some of the
|
|
1113 variables that @code{mode-line-format} refers to.
|
6451
|
1114
|
7253
|
1115 A mode line construct may be a list, a symbol, or a string. If the
|
|
1116 value is a list, each element may be a list, a symbol, or a string.
|
6451
|
1117
|
25751
|
1118 The mode line can display various faces, if the strings that control
|
|
1119 it have the @code{face} property. @xref{Properties in Mode}. In
|
|
1120 addition, the face @code{mode-line} is used as a default for the whole
|
|
1121 mode line (@pxref{Standard Faces}).
|
|
1122
|
6451
|
1123 @table @code
|
|
1124 @cindex percent symbol in mode line
|
|
1125 @item @var{string}
|
|
1126 A string as a mode line construct is displayed verbatim in the mode line
|
12098
|
1127 except for @dfn{@code{%}-constructs}. Decimal digits after the @samp{%}
|
6451
|
1128 specify the field width for space filling on the right (i.e., the data
|
|
1129 is left justified). @xref{%-Constructs}.
|
|
1130
|
|
1131 @item @var{symbol}
|
|
1132 A symbol as a mode line construct stands for its value. The value of
|
7253
|
1133 @var{symbol} is used as a mode line construct, in place of @var{symbol}.
|
25751
|
1134 However, the symbols @code{t} and @code{nil} are ignored, as is any
|
7253
|
1135 symbol whose value is void.
|
6451
|
1136
|
|
1137 There is one exception: if the value of @var{symbol} is a string, it is
|
7253
|
1138 displayed verbatim: the @code{%}-constructs are not recognized.
|
6451
|
1139
|
|
1140 @item (@var{string} @var{rest}@dots{}) @r{or} (@var{list} @var{rest}@dots{})
|
7253
|
1141 A list whose first element is a string or list means to process all the
|
|
1142 elements recursively and concatenate the results. This is the most
|
|
1143 common form of mode line construct.
|
6451
|
1144
|
25751
|
1145 @item (:eval @var{form})
|
|
1146 A list whose first element is the symbol @code{:eval} says to evaluate
|
|
1147 @var{form}, and use the result as a string to display.
|
|
1148 (This feature is new as of Emacs 21.)
|
|
1149
|
6451
|
1150 @item (@var{symbol} @var{then} @var{else})
|
25751
|
1151 A list whose first element is a symbol that is not a keyword specifies a
|
|
1152 conditional. Its meaning depends on the value of @var{symbol}. If the
|
|
1153 value is non-@code{nil}, the second element, @var{then}, is processed
|
|
1154 recursively as a mode line element. But if the value of @var{symbol} is
|
|
1155 @code{nil}, the third element, @var{else}, is processed recursively.
|
|
1156 You may omit @var{else}; then the mode line element displays nothing if
|
|
1157 the value of @var{symbol} is @code{nil}.
|
6451
|
1158
|
|
1159 @item (@var{width} @var{rest}@dots{})
|
|
1160 A list whose first element is an integer specifies truncation or
|
|
1161 padding of the results of @var{rest}. The remaining elements
|
|
1162 @var{rest} are processed recursively as mode line constructs and
|
|
1163 concatenated together. Then the result is space filled (if
|
|
1164 @var{width} is positive) or truncated (to @minus{}@var{width} columns,
|
|
1165 if @var{width} is negative) on the right.
|
|
1166
|
|
1167 For example, the usual way to show what percentage of a buffer is above
|
7253
|
1168 the top of the window is to use a list like this: @code{(-3 "%p")}.
|
6451
|
1169 @end table
|
|
1170
|
|
1171 If you do alter @code{mode-line-format} itself, the new value should
|
7253
|
1172 use the same variables that appear in the default value (@pxref{Mode
|
|
1173 Line Variables}), rather than duplicating their contents or displaying
|
|
1174 the information in another fashion. This way, customizations made by
|
12098
|
1175 the user or by Lisp programs (such as @code{display-time} and major
|
|
1176 modes) via changes to those variables remain effective.
|
6451
|
1177
|
|
1178 @cindex Shell mode @code{mode-line-format}
|
|
1179 Here is an example of a @code{mode-line-format} that might be
|
21682
|
1180 useful for @code{shell-mode}, since it contains the host name and default
|
6451
|
1181 directory.
|
|
1182
|
|
1183 @example
|
|
1184 @group
|
|
1185 (setq mode-line-format
|
21682
|
1186 (list "-"
|
|
1187 'mode-line-mule-info
|
6451
|
1188 'mode-line-modified
|
21682
|
1189 'mode-line-frame-identification
|
6451
|
1190 "%b--"
|
|
1191 @end group
|
21007
|
1192 @group
|
|
1193 ;; @r{Note that this is evaluated while making the list.}
|
|
1194 ;; @r{It makes a mode line construct which is just a string.}
|
|
1195 (getenv "HOST")
|
|
1196 @end group
|
6451
|
1197 ":"
|
|
1198 'default-directory
|
|
1199 " "
|
|
1200 'global-mode-string
|
7253
|
1201 " %[("
|
25751
|
1202 '(:eval (mode-line-mode-name))
|
7253
|
1203 'mode-line-process
|
6451
|
1204 'minor-mode-alist
|
|
1205 "%n"
|
21682
|
1206 ")%]--"
|
6451
|
1207 @group
|
21682
|
1208 '(which-func-mode ("" which-func-format "--"))
|
12098
|
1209 '(line-number-mode "L%l--")
|
21682
|
1210 '(column-number-mode "C%c--")
|
6451
|
1211 '(-3 . "%p")
|
|
1212 "-%-"))
|
|
1213 @end group
|
|
1214 @end example
|
|
1215
|
22252
|
1216 @noindent
|
|
1217 (The variables @code{line-number-mode}, @code{column-number-mode}
|
|
1218 and @code{which-func-mode} enable particular minor modes; as usual,
|
|
1219 these variable names are also the minor mode command names.)
|
|
1220
|
6451
|
1221 @node Mode Line Variables
|
|
1222 @subsection Variables Used in the Mode Line
|
|
1223
|
|
1224 This section describes variables incorporated by the
|
|
1225 standard value of @code{mode-line-format} into the text of the mode
|
|
1226 line. There is nothing inherently special about these variables; any
|
|
1227 other variables could have the same effects on the mode line if
|
|
1228 @code{mode-line-format} were changed to use them.
|
|
1229
|
22138
|
1230 @defvar mode-line-mule-info
|
21682
|
1231 This variable holds the value of the mode-line construct that displays
|
|
1232 information about the language environment, buffer coding system, and
|
22138
|
1233 current input method. @xref{Non-ASCII Characters}.
|
21682
|
1234 @end defvar
|
|
1235
|
6451
|
1236 @defvar mode-line-modified
|
7253
|
1237 This variable holds the value of the mode-line construct that displays
|
6451
|
1238 whether the current buffer is modified.
|
|
1239
|
21682
|
1240 The default value of @code{mode-line-modified} is @code{("%1*%1+")}.
|
|
1241 This means that the mode line displays @samp{**} if the buffer is
|
|
1242 modified, @samp{--} if the buffer is not modified, @samp{%%} if the
|
|
1243 buffer is read only, and @samp{%*} if the buffer is read only and
|
|
1244 modified.
|
6451
|
1245
|
|
1246 Changing this variable does not force an update of the mode line.
|
|
1247 @end defvar
|
|
1248
|
22138
|
1249 @defvar mode-line-frame-identification
|
21682
|
1250 This variable identifies the current frame. The default value is
|
|
1251 @code{" "} if you are using a window system which can show multiple
|
|
1252 frames, or @code{"-%F "} on an ordinary terminal which shows only one
|
|
1253 frame at a time.
|
|
1254 @end defvar
|
|
1255
|
6451
|
1256 @defvar mode-line-buffer-identification
|
7253
|
1257 This variable identifies the buffer being displayed in the window. Its
|
22267
|
1258 default value is @code{("%12b")}, which displays the buffer name, padded
|
|
1259 with spaces to at least 12 columns.
|
6451
|
1260 @end defvar
|
|
1261
|
|
1262 @defvar global-mode-string
|
|
1263 This variable holds a mode line spec that appears in the mode line by
|
|
1264 default, just after the buffer name. The command @code{display-time}
|
|
1265 sets @code{global-mode-string} to refer to the variable
|
|
1266 @code{display-time-string}, which holds a string containing the time and
|
|
1267 load information.
|
|
1268
|
|
1269 The @samp{%M} construct substitutes the value of
|
21007
|
1270 @code{global-mode-string}, but that is obsolete, since the variable is
|
|
1271 included in the mode line from @code{mode-line-format}.
|
6451
|
1272 @end defvar
|
|
1273
|
|
1274 @defvar mode-name
|
7253
|
1275 This buffer-local variable holds the ``pretty'' name of the current
|
6451
|
1276 buffer's major mode. Each major mode should set this variable so that the
|
|
1277 mode name will appear in the mode line.
|
|
1278 @end defvar
|
|
1279
|
|
1280 @defvar minor-mode-alist
|
7253
|
1281 This variable holds an association list whose elements specify how the
|
6451
|
1282 mode line should indicate that a minor mode is active. Each element of
|
|
1283 the @code{minor-mode-alist} should be a two-element list:
|
|
1284
|
|
1285 @example
|
|
1286 (@var{minor-mode-variable} @var{mode-line-string})
|
|
1287 @end example
|
|
1288
|
|
1289 More generally, @var{mode-line-string} can be any mode line spec. It
|
|
1290 appears in the mode line when the value of @var{minor-mode-variable} is
|
|
1291 non-@code{nil}, and not otherwise. These strings should begin with
|
|
1292 spaces so that they don't run together. Conventionally, the
|
|
1293 @var{minor-mode-variable} for a specific mode is set to a non-@code{nil}
|
|
1294 value when that minor mode is activated.
|
|
1295
|
|
1296 The default value of @code{minor-mode-alist} is:
|
|
1297
|
|
1298 @example
|
|
1299 @group
|
|
1300 minor-mode-alist
|
12098
|
1301 @result{} ((vc-mode vc-mode)
|
|
1302 (abbrev-mode " Abbrev")
|
|
1303 (overwrite-mode overwrite-mode)
|
6451
|
1304 (auto-fill-function " Fill")
|
12098
|
1305 (defining-kbd-macro " Def")
|
|
1306 (isearch-mode isearch-mode))
|
6451
|
1307 @end group
|
|
1308 @end example
|
|
1309
|
21007
|
1310 @code{minor-mode-alist} itself is not buffer-local. Each variable
|
|
1311 mentioned in the alist should be buffer-local if its minor mode can be
|
|
1312 enabled separately in each buffer.
|
6451
|
1313 @end defvar
|
|
1314
|
|
1315 @defvar mode-line-process
|
|
1316 This buffer-local variable contains the mode line information on process
|
|
1317 status in modes used for communicating with subprocesses. It is
|
|
1318 displayed immediately following the major mode name, with no intervening
|
|
1319 space. For example, its value in the @samp{*shell*} buffer is
|
22252
|
1320 @code{(":%s")}, which allows the shell to display its status along
|
25875
|
1321 with the major mode as: @samp{(Shell:run)}. Normally this variable
|
6451
|
1322 is @code{nil}.
|
|
1323 @end defvar
|
|
1324
|
25875
|
1325 Some variables are used by @code{minor-mode-alist} to display
|
|
1326 a string for various minor modes when enabled. This is a typical
|
|
1327 example:
|
|
1328
|
|
1329 @defvar vc-mode
|
|
1330 The variable @code{vc-mode}, buffer-local in each buffer, records
|
|
1331 whether the buffer's visited file is maintained with version control,
|
|
1332 and, if so, which kind. Its value is a string that appears in the mode
|
|
1333 line, or @code{nil} for no version control.
|
|
1334 @end defvar
|
|
1335
|
|
1336 The variable @code{default-mode-line-format} is where
|
|
1337 @code{mode-line-format} usually gets its value:
|
|
1338
|
6451
|
1339 @defvar default-mode-line-format
|
7253
|
1340 This variable holds the default @code{mode-line-format} for buffers
|
6451
|
1341 that do not override it. This is the same as @code{(default-value
|
|
1342 'mode-line-format)}.
|
|
1343
|
21007
|
1344 The default value of @code{default-mode-line-format} is this list:
|
6451
|
1345
|
|
1346 @example
|
|
1347 @group
|
21007
|
1348 ("-"
|
|
1349 mode-line-mule-info
|
6451
|
1350 mode-line-modified
|
21007
|
1351 mode-line-frame-identification
|
6451
|
1352 mode-line-buffer-identification
|
21007
|
1353 @end group
|
6451
|
1354 " "
|
|
1355 global-mode-string
|
21007
|
1356 @group
|
6451
|
1357 " %[("
|
25875
|
1358 ;; @r{@code{mode-line-mode-name} is a function}
|
26211
|
1359 ;; @r{that copies the mode name and adds text}
|
25875
|
1360 ;; @r{properties to make it mouse-sensitive.}
|
25751
|
1361 (:eval (mode-line-mode-name))
|
12098
|
1362 mode-line-process
|
6451
|
1363 minor-mode-alist
|
|
1364 "%n"
|
21007
|
1365 ")%]--"
|
|
1366 @end group
|
|
1367 @group
|
|
1368 (which-func-mode ("" which-func-format "--"))
|
12098
|
1369 (line-number-mode "L%l--")
|
21007
|
1370 (column-number-mode "C%c--")
|
6451
|
1371 (-3 . "%p")
|
|
1372 "-%-")
|
|
1373 @end group
|
|
1374 @end example
|
|
1375 @end defvar
|
|
1376
|
|
1377 @node %-Constructs
|
|
1378 @subsection @code{%}-Constructs in the Mode Line
|
|
1379
|
|
1380 The following table lists the recognized @code{%}-constructs and what
|
7253
|
1381 they mean. In any construct except @samp{%%}, you can add a decimal
|
|
1382 integer after the @samp{%} to specify how many characters to display.
|
6451
|
1383
|
|
1384 @table @code
|
|
1385 @item %b
|
|
1386 The current buffer name, obtained with the @code{buffer-name} function.
|
|
1387 @xref{Buffer Names}.
|
|
1388
|
25875
|
1389 @item %c
|
|
1390 The current column number of point.
|
|
1391
|
6451
|
1392 @item %f
|
|
1393 The visited file name, obtained with the @code{buffer-file-name}
|
|
1394 function. @xref{Buffer File Name}.
|
|
1395
|
12067
|
1396 @item %F
|
21682
|
1397 The title (only on a window system) or the name of the selected frame.
|
|
1398 @xref{Window Frame Parameters}.
|
12067
|
1399
|
|
1400 @item %l
|
25751
|
1401 The current line number of point, counting within the accessible portion
|
|
1402 of the buffer.
|
12067
|
1403
|
25875
|
1404 @item %n
|
|
1405 @samp{Narrow} when narrowing is in effect; nothing otherwise (see
|
|
1406 @code{narrow-to-region} in @ref{Narrowing}).
|
|
1407
|
|
1408 @item %p
|
|
1409 The percentage of the buffer text above the @strong{top} of window, or
|
|
1410 @samp{Top}, @samp{Bottom} or @samp{All}. Note that the default
|
|
1411 mode-line specification truncates this to three characters.
|
|
1412
|
|
1413 @item %P
|
|
1414 The percentage of the buffer text that is above the @strong{bottom} of
|
|
1415 the window (which includes the text visible in the window, as well as
|
|
1416 the text above the top), plus @samp{Top} if the top of the buffer is
|
|
1417 visible on screen; or @samp{Bottom} or @samp{All}.
|
|
1418
|
|
1419 @item %s
|
|
1420 The status of the subprocess belonging to the current buffer, obtained with
|
|
1421 @code{process-status}. @xref{Process Information}.
|
|
1422
|
|
1423 @item %t
|
|
1424 Whether the visited file is a text file or a binary file. This is a
|
|
1425 meaningful distinction only on certain operating systems (@pxref{MS-DOS
|
|
1426 File Types}).
|
|
1427
|
6451
|
1428 @item %*
|
|
1429 @samp{%} if the buffer is read only (see @code{buffer-read-only}); @*
|
|
1430 @samp{*} if the buffer is modified (see @code{buffer-modified-p}); @*
|
|
1431 @samp{-} otherwise. @xref{Buffer Modification}.
|
|
1432
|
|
1433 @item %+
|
12067
|
1434 @samp{*} if the buffer is modified (see @code{buffer-modified-p}); @*
|
|
1435 @samp{%} if the buffer is read only (see @code{buffer-read-only}); @*
|
|
1436 @samp{-} otherwise. This differs from @samp{%*} only for a modified
|
|
1437 read-only buffer. @xref{Buffer Modification}.
|
|
1438
|
|
1439 @item %&
|
7253
|
1440 @samp{*} if the buffer is modified, and @samp{-} otherwise.
|
6451
|
1441
|
|
1442 @item %[
|
|
1443 An indication of the depth of recursive editing levels (not counting
|
|
1444 minibuffer levels): one @samp{[} for each editing level.
|
|
1445 @xref{Recursive Editing}.
|
|
1446
|
|
1447 @item %]
|
|
1448 One @samp{]} for each recursive editing level (not counting minibuffer
|
|
1449 levels).
|
|
1450
|
25875
|
1451 @item %-
|
|
1452 Dashes sufficient to fill the remainder of the mode line.
|
|
1453
|
6451
|
1454 @item %%
|
|
1455 The character @samp{%}---this is how to include a literal @samp{%} in a
|
|
1456 string in which @code{%}-constructs are allowed.
|
|
1457 @end table
|
|
1458
|
|
1459 The following two @code{%}-constructs are still supported, but they are
|
|
1460 obsolete, since you can get the same results with the variables
|
|
1461 @code{mode-name} and @code{global-mode-string}.
|
|
1462
|
|
1463 @table @code
|
|
1464 @item %m
|
|
1465 The value of @code{mode-name}.
|
|
1466
|
|
1467 @item %M
|
|
1468 The value of @code{global-mode-string}. Currently, only
|
|
1469 @code{display-time} modifies the value of @code{global-mode-string}.
|
|
1470 @end table
|
|
1471
|
25751
|
1472 @node Properties in Mode
|
|
1473 @subsection Properties in the Mode Line
|
|
1474
|
|
1475 Starting in Emacs 21, certain text properties are meaningful in the
|
|
1476 mode line. The @code{face} property affects the appearance of text; the
|
|
1477 @code{help-echo} property associate help strings with the text, and
|
29102
|
1478 @code{local-map} can make the text mouse-sensitive.
|
25751
|
1479
|
|
1480 There are three ways to specify text properties for text in the mode
|
|
1481 line:
|
|
1482
|
|
1483 @enumerate
|
|
1484 @item
|
29102
|
1485 Put a string with the @code{local-map} property directly into the
|
|
1486 mode-line data structure.
|
25751
|
1487
|
|
1488 @item
|
29102
|
1489 Put a @code{local-map} property on a mode-line %-construct
|
|
1490 such as @samp{%12b}; then the expansion of the %-construct
|
|
1491 will have that same text property.
|
25751
|
1492
|
|
1493 @item
|
|
1494 Use a list containing @code{:eval @var{form}} in the mode-line data
|
|
1495 structure, and make @var{form} evaluate to a string that has a
|
29102
|
1496 @code{local-map} property.
|
25751
|
1497 @end enumerate
|
|
1498
|
29102
|
1499 You use the @code{local-map} property to specify a keymap. Like any
|
25751
|
1500 keymap, it can bind character keys and function keys; but that has no
|
25875
|
1501 effect, since it is impossible to move point into the mode line. This
|
25751
|
1502 keymap can only take real effect for mouse clicks.
|
|
1503
|
|
1504 @node Header Lines
|
|
1505 @subsection Window Header Lines
|
|
1506 @cindex header line (of a window)
|
|
1507 @cindex window header line
|
|
1508
|
|
1509 Starting in Emacs 21, a window can have a @dfn{header line} at the
|
|
1510 top, just as it can have a mode line at the bottom. The header line
|
|
1511 feature works just like the mode line feature, except that it's
|
|
1512 controlled by different variables.
|
|
1513
|
|
1514 @tindex header-line-format
|
|
1515 @defvar header-line-format
|
|
1516 This variable, local in every buffer, specifies how to display the
|
|
1517 header line, for windows displaying the buffer. The format of the value
|
26783
|
1518 is the same as for @code{mode-line-format} (@pxref{Mode Line Data}).
|
25751
|
1519 @end defvar
|
|
1520
|
|
1521 @tindex default-header-line-format
|
|
1522 @defvar default-header-line-format
|
|
1523 This variable holds the default @code{header-line-format} for buffers
|
|
1524 that do not override it. This is the same as @code{(default-value
|
|
1525 'header-line-format)}.
|
|
1526
|
|
1527 It is normally @code{nil}, so that ordinary buffers have no header line.
|
|
1528 @end defvar
|
|
1529
|
21007
|
1530 @node Imenu
|
|
1531 @section Imenu
|
|
1532
|
|
1533 @cindex Imenu
|
21682
|
1534 @dfn{Imenu} is a feature that lets users select a definition or
|
|
1535 section in the buffer, from a menu which lists all of them, to go
|
|
1536 directly to that location in the buffer. Imenu works by constructing a
|
25751
|
1537 buffer index which lists the names and buffer positions of the
|
25875
|
1538 definitions, or other named portions of the buffer; then the user can
|
|
1539 choose one of them and move point to it. This section explains how to
|
|
1540 customize how Imenu finds the definitions or buffer portions for a
|
|
1541 particular major mode.
|
21682
|
1542
|
|
1543 The usual and simplest way is to set the variable
|
|
1544 @code{imenu-generic-expression}:
|
21007
|
1545
|
|
1546 @defvar imenu-generic-expression
|
|
1547 This variable, if non-@code{nil}, specifies regular expressions for
|
|
1548 finding definitions for Imenu. In the simplest case, elements should
|
|
1549 look like this:
|
|
1550
|
|
1551 @example
|
|
1552 (@var{menu-title} @var{regexp} @var{subexp})
|
|
1553 @end example
|
|
1554
|
|
1555 Here, if @var{menu-title} is non-@code{nil}, it says that the matches
|
|
1556 for this element should go in a submenu of the buffer index;
|
|
1557 @var{menu-title} itself specifies the name for the submenu. If
|
|
1558 @var{menu-title} is @code{nil}, the matches for this element go directly
|
|
1559 in the top level of the buffer index.
|
|
1560
|
|
1561 The second item in the list, @var{regexp}, is a regular expression
|
25751
|
1562 (@pxref{Regular Expressions}); anything in the buffer that it matches is
|
25875
|
1563 considered a definition, something to mention in the buffer index. The
|
|
1564 third item, @var{subexp}, indicates which subexpression in @var{regexp}
|
25751
|
1565 matches the definition's name.
|
21007
|
1566
|
|
1567 An element can also look like this:
|
|
1568
|
|
1569 @example
|
|
1570 (@var{menu-title} @var{regexp} @var{index} @var{function} @var{arguments}@dots{})
|
|
1571 @end example
|
|
1572
|
|
1573 Each match for this element creates a special index item which, if
|
25875
|
1574 selected by the user, calls @var{function} with arguments consisting of
|
|
1575 the item name, the buffer position, and @var{arguments}.
|
21007
|
1576
|
|
1577 For Emacs Lisp mode, @var{pattern} could look like this:
|
|
1578
|
22138
|
1579 @c should probably use imenu-syntax-alist and \\sw rather than [-A-Za-z0-9+]
|
21007
|
1580 @example
|
|
1581 @group
|
|
1582 ((nil "^\\s-*(def\\(un\\|subst\\|macro\\|advice\\)\
|
|
1583 \\s-+\\([-A-Za-z0-9+]+\\)" 2)
|
|
1584 @end group
|
|
1585 @group
|
|
1586 ("*Vars*" "^\\s-*(def\\(var\\|const\\)\
|
|
1587 \\s-+\\([-A-Za-z0-9+]+\\)" 2)
|
|
1588 @end group
|
|
1589 @group
|
|
1590 ("*Types*"
|
22138
|
1591 "^\\s-*\
|
|
1592 (def\\(type\\|struct\\|class\\|ine-condition\\)\
|
21007
|
1593 \\s-+\\([-A-Za-z0-9+]+\\)" 2))
|
|
1594 @end group
|
|
1595 @end example
|
|
1596
|
21682
|
1597 Setting this variable makes it buffer-local in the current buffer.
|
21007
|
1598 @end defvar
|
|
1599
|
|
1600 @defvar imenu-case-fold-search
|
22138
|
1601 This variable controls whether matching against
|
|
1602 @var{imenu-generic-expression} is case-sensitive: @code{t}, the default,
|
|
1603 means matching should ignore case.
|
|
1604
|
|
1605 Setting this variable makes it buffer-local in the current buffer.
|
|
1606 @end defvar
|
|
1607
|
|
1608 @defvar imenu-syntax-alist
|
|
1609 This variable is an alist of syntax table modifiers to use while
|
22252
|
1610 processing @code{imenu-generic-expression}, to override the syntax table
|
|
1611 of the current buffer. Each element should have this form:
|
22138
|
1612
|
|
1613 @example
|
|
1614 (@var{characters} . @var{syntax-description})
|
|
1615 @end example
|
|
1616
|
|
1617 The @sc{car}, @var{characters}, can be either a character or a string.
|
|
1618 The element says to give that character or characters the syntax
|
|
1619 specified by @var{syntax-description}, which is passed to
|
|
1620 @code{modify-syntax-entry} (@pxref{Syntax Table Functions}).
|
|
1621
|
|
1622 This feature is typically used to give word syntax to characters which
|
|
1623 normally have symbol syntax, and thus to simplify
|
|
1624 @code{imenu-generic-expression} and speed up matching.
|
|
1625 For example, Fortran mode uses it this way:
|
|
1626
|
|
1627 @example
|
|
1628 (setq imenu-syntax-alist '(("_$" . "w")))
|
|
1629 @end example
|
|
1630
|
|
1631 The @code{imenu-generic-expression} patterns can then use @samp{\\sw+}
|
22252
|
1632 instead of @samp{\\(\\sw\\|\\s_\\)+}. Note that this technique may be
|
25751
|
1633 inconvenient when the mode needs to limit the initial character
|
22267
|
1634 of a name to a smaller set of characters than are allowed in the rest
|
|
1635 of a name.
|
21007
|
1636
|
21682
|
1637 Setting this variable makes it buffer-local in the current buffer.
|
21007
|
1638 @end defvar
|
|
1639
|
|
1640 Another way to customize Imenu for a major mode is to set the
|
|
1641 variables @code{imenu-prev-index-position-function} and
|
21682
|
1642 @code{imenu-extract-index-name-function}:
|
21007
|
1643
|
|
1644 @defvar imenu-prev-index-position-function
|
27332
|
1645 If this variable is non-@code{nil}, its value should be a function that
|
25875
|
1646 finds the next ``definition'' to put in the buffer index, scanning
|
|
1647 backward in the buffer from point. It should return @code{nil} if it
|
|
1648 doesn't find another ``definition'' before point. Otherwise it shuould
|
|
1649 leave point at the place it finds a ``definition,'' and return any
|
|
1650 non-@code{nil} value.
|
21007
|
1651
|
21682
|
1652 Setting this variable makes it buffer-local in the current buffer.
|
21007
|
1653 @end defvar
|
|
1654
|
|
1655 @defvar imenu-extract-index-name-function
|
|
1656 If this variable is non-@code{nil}, its value should be a function to
|
21682
|
1657 return the name for a definition, assuming point is in that definition
|
|
1658 as the @code{imenu-prev-index-position-function} function would leave
|
|
1659 it.
|
21007
|
1660
|
21682
|
1661 Setting this variable makes it buffer-local in the current buffer.
|
21007
|
1662 @end defvar
|
|
1663
|
21682
|
1664 The last way to customize Imenu for a major mode is to set the
|
25875
|
1665 variable @code{imenu-create-index-function}:
|
21682
|
1666
|
21007
|
1667 @defvar imenu-create-index-function
|
|
1668 This variable specifies the function to use for creating a buffer index.
|
|
1669 The function should take no arguments, and return an index for the
|
|
1670 current buffer. It is called within @code{save-excursion}, so where it
|
|
1671 leaves point makes no difference.
|
|
1672
|
|
1673 The default value is a function that uses
|
|
1674 @code{imenu-generic-expression} to produce the index alist. If you
|
|
1675 specify a different function, then @code{imenu-generic-expression} is
|
|
1676 not used.
|
|
1677
|
21682
|
1678 Setting this variable makes it buffer-local in the current buffer.
|
21007
|
1679 @end defvar
|
|
1680
|
|
1681 @defvar imenu-index-alist
|
|
1682 This variable holds the index alist for the current buffer.
|
21682
|
1683 Setting it makes it buffer-local in the current buffer.
|
21007
|
1684
|
|
1685 Simple elements in the alist look like @code{(@var{index-name}
|
|
1686 . @var{index-position})}. Selecting a simple element has the effect of
|
|
1687 moving to position @var{index-position} in the buffer.
|
|
1688
|
|
1689 Special elements look like @code{(@var{index-name} @var{position}
|
|
1690 @var{function} @var{arguments}@dots{})}. Selecting a special element
|
|
1691 performs
|
|
1692
|
|
1693 @example
|
|
1694 (funcall @var{function} @var{index-name} @var{position} @var{arguments}@dots{})
|
|
1695 @end example
|
|
1696
|
|
1697 A nested sub-alist element looks like @code{(@var{index-name}
|
|
1698 @var{sub-alist})}.
|
|
1699 @end defvar
|
|
1700
|
|
1701 @node Font Lock Mode
|
|
1702 @section Font Lock Mode
|
|
1703 @cindex Font Lock Mode
|
|
1704
|
|
1705 @dfn{Font Lock mode} is a feature that automatically attaches
|
|
1706 @code{face} properties to certain parts of the buffer based on their
|
|
1707 syntactic role. How it parses the buffer depends on the major mode;
|
25875
|
1708 most major modes define syntactic criteria for which faces to use in
|
21682
|
1709 which contexts. This section explains how to customize Font Lock for a
|
25875
|
1710 particular major mode.
|
21007
|
1711
|
|
1712 Font Lock mode finds text to highlight in two ways: through syntactic
|
|
1713 parsing based on the syntax table, and through searching (usually for
|
|
1714 regular expressions). Syntactic fontification happens first; it finds
|
|
1715 comments and string constants, and highlights them using
|
|
1716 @code{font-lock-comment-face} and @code{font-lock-string-face}
|
25875
|
1717 (@pxref{Faces for Font Lock}). Search-based fontification follows.
|
21007
|
1718
|
|
1719 @menu
|
|
1720 * Font Lock Basics::
|
|
1721 * Search-based Fontification::
|
|
1722 * Other Font Lock Variables::
|
|
1723 * Levels of Font Lock::
|
|
1724 * Faces for Font Lock::
|
21682
|
1725 * Syntactic Font Lock::
|
21007
|
1726 @end menu
|
|
1727
|
|
1728 @node Font Lock Basics
|
|
1729 @subsection Font Lock Basics
|
|
1730
|
|
1731 There are several variables that control how Font Lock mode highlights
|
|
1732 text. But major modes should not set any of these variables directly.
|
24934
|
1733 Instead, they should set @code{font-lock-defaults} as a buffer-local
|
21682
|
1734 variable. The value assigned to this variable is used, if and when Font
|
|
1735 Lock mode is enabled, to set all the other variables.
|
21007
|
1736
|
|
1737 @defvar font-lock-defaults
|
|
1738 This variable is set by major modes, as a buffer-local variable, to
|
|
1739 specify how to fontify text in that mode. The value should look like
|
|
1740 this:
|
|
1741
|
|
1742 @example
|
|
1743 (@var{keywords} @var{keywords-only} @var{case-fold}
|
|
1744 @var{syntax-alist} @var{syntax-begin} @var{other-vars}@dots{})
|
|
1745 @end example
|
|
1746
|
|
1747 The first element, @var{keywords}, indirectly specifies the value of
|
|
1748 @code{font-lock-keywords}. It can be a symbol, a variable whose value
|
25875
|
1749 is the list to use for @code{font-lock-keywords}. It can also be a list of
|
21007
|
1750 several such symbols, one for each possible level of fontification. The
|
|
1751 first symbol specifies how to do level 1 fontification, the second
|
|
1752 symbol how to do level 2, and so on.
|
|
1753
|
|
1754 The second element, @var{keywords-only}, specifies the value of the
|
22138
|
1755 variable @code{font-lock-keywords-only}. If this is non-@code{nil},
|
21682
|
1756 syntactic fontification (of strings and comments) is not performed.
|
21007
|
1757
|
|
1758 The third element, @var{case-fold}, specifies the value of
|
|
1759 @code{font-lock-case-fold-search}. If it is non-@code{nil}, Font Lock
|
21682
|
1760 mode ignores case when searching as directed by
|
|
1761 @code{font-lock-keywords}.
|
21007
|
1762
|
|
1763 If the fourth element, @var{syntax-alist}, is non-@code{nil}, it should be
|
|
1764 a list of cons cells of the form @code{(@var{char-or-string}
|
|
1765 . @var{string})}. These are used to set up a syntax table for
|
|
1766 fontification (@pxref{Syntax Table Functions}). The resulting syntax
|
|
1767 table is stored in @code{font-lock-syntax-table}.
|
|
1768
|
|
1769 The fifth element, @var{syntax-begin}, specifies the value of
|
21682
|
1770 @code{font-lock-beginning-of-syntax-function} (see below).
|
21007
|
1771
|
25875
|
1772 All the remaining elements (if any) are collectively called
|
|
1773 @var{other-vars}. Each of these elements should have the form
|
|
1774 @code{(@var{variable} . @var{value})}---which means, make @var{variable}
|
|
1775 buffer-local and then set it to @var{value}. You can use these
|
|
1776 @var{other-vars} to set other variables that affect fontification,
|
|
1777 aside from those you can control with the first five elements.
|
21007
|
1778 @end defvar
|
|
1779
|
|
1780 @node Search-based Fontification
|
|
1781 @subsection Search-based Fontification
|
|
1782
|
|
1783 The most important variable for customizing Font Lock mode is
|
|
1784 @code{font-lock-keywords}. It specifies the search criteria for
|
|
1785 search-based fontification.
|
|
1786
|
|
1787 @defvar font-lock-keywords
|
|
1788 This variable's value is a list of the keywords to highlight. Be
|
21682
|
1789 careful when composing regular expressions for this list; a poorly
|
|
1790 written pattern can dramatically slow things down!
|
21007
|
1791 @end defvar
|
|
1792
|
|
1793 Each element of @code{font-lock-keywords} specifies how to find
|
21682
|
1794 certain cases of text, and how to highlight those cases. Font Lock mode
|
|
1795 processes the elements of @code{font-lock-keywords} one by one, and for
|
|
1796 each element, it finds and handles all matches. Ordinarily, once
|
|
1797 part of the text has been fontified already, this cannot be overridden
|
|
1798 by a subsequent match in the same text; but you can specify different
|
|
1799 behavior using the @var{override} element of a @var{highlighter}.
|
|
1800
|
|
1801 Each element of @code{font-lock-keywords} should have one of these
|
|
1802 forms:
|
21007
|
1803
|
|
1804 @table @code
|
|
1805 @item @var{regexp}
|
|
1806 Highlight all matches for @var{regexp} using
|
|
1807 @code{font-lock-keyword-face}. For example,
|
|
1808
|
|
1809 @example
|
|
1810 ;; @r{Highlight discrete occurrences of @samp{foo}}
|
|
1811 ;; @r{using @code{font-lock-keyword-face}.}
|
|
1812 "\\<foo\\>"
|
|
1813 @end example
|
|
1814
|
21682
|
1815 The function @code{regexp-opt} (@pxref{Syntax of Regexps}) is useful for
|
|
1816 calculating optimal regular expressions to match a number of different
|
|
1817 keywords.
|
21007
|
1818
|
|
1819 @item @var{function}
|
|
1820 Find text by calling @var{function}, and highlight the matches
|
|
1821 it finds using @code{font-lock-keyword-face}.
|
|
1822
|
|
1823 When @var{function} is called, it receives one argument, the limit of
|
|
1824 the search. It should return non-@code{nil} if it succeeds, and set the
|
|
1825 match data to describe the match that was found.
|
|
1826
|
|
1827 @item (@var{matcher} . @var{match})
|
24934
|
1828 In this kind of element, @var{matcher} is either a regular
|
21007
|
1829 expression or a function, as described above. The @sc{cdr},
|
|
1830 @var{match}, specifies which subexpression of @var{matcher} should be
|
21682
|
1831 highlighted (instead of the entire text that @var{matcher} matched).
|
21007
|
1832
|
|
1833 @example
|
25751
|
1834 ;; @r{Highlight the @samp{bar} in each occurrence of @samp{fubar},}
|
21007
|
1835 ;; @r{using @code{font-lock-keyword-face}.}
|
|
1836 ("fu\\(bar\\)" . 1)
|
|
1837 @end example
|
|
1838
|
21682
|
1839 If you use @code{regexp-opt} to produce the regular expression
|
21007
|
1840 @var{matcher}, then you can use @code{regexp-opt-depth} (@pxref{Syntax
|
|
1841 of Regexps}) to calculate the value for @var{match}.
|
|
1842
|
|
1843 @item (@var{matcher} . @var{facename})
|
|
1844 In this kind of element, @var{facename} is an expression whose value
|
|
1845 specifies the face name to use for highlighting.
|
|
1846
|
|
1847 @example
|
|
1848 ;; @r{Highlight occurrences of @samp{fubar},}
|
|
1849 ;; @r{using the face which is the value of @code{fubar-face}.}
|
|
1850 ("fubar" . fubar-face)
|
|
1851 @end example
|
|
1852
|
|
1853 @item (@var{matcher} . @var{highlighter})
|
|
1854 In this kind of element, @var{highlighter} is a list
|
|
1855 which specifies how to highlight matches found by @var{matcher}.
|
|
1856 It has the form
|
|
1857
|
|
1858 @example
|
|
1859 (@var{subexp} @var{facename} @var{override} @var{laxmatch})
|
|
1860 @end example
|
|
1861
|
|
1862 The @sc{car}, @var{subexp}, is an integer specifying which subexpression
|
21682
|
1863 of the match to fontify (0 means the entire matching text). The second
|
|
1864 subelement, @var{facename}, specifies the face, as described above.
|
21007
|
1865
|
|
1866 The last two values in @var{highlighter}, @var{override} and
|
|
1867 @var{laxmatch}, are flags. If @var{override} is @code{t}, this element
|
|
1868 can override existing fontification made by previous elements of
|
|
1869 @code{font-lock-keywords}. If it is @code{keep}, then each character is
|
|
1870 fontified if it has not been fontified already by some other element.
|
|
1871 If it is @code{prepend}, the face @var{facename} is added to the
|
|
1872 beginning of the @code{face} property. If it is @code{append}, the face
|
|
1873 @var{facename} is added to the end of the @code{face} property.
|
|
1874
|
|
1875 If @var{laxmatch} is non-@code{nil}, it means there should be no error
|
|
1876 if there is no subexpression numbered @var{subexp} in @var{matcher}.
|
25975
|
1877 Obviously, fontification of the subexpression numbered @var{subexp} will
|
|
1878 not occur. However, fontification of other subexpressions (and other
|
|
1879 regexps) will continue. If @var{laxmatch} is @code{nil}, and the
|
|
1880 specified subexpression is missing, then an error is signalled which
|
|
1881 terminates search-based fontification.
|
21007
|
1882
|
|
1883 Here are some examples of elements of this kind, and what they do:
|
|
1884
|
|
1885 @smallexample
|
|
1886 ;; @r{Highlight occurrences of either @samp{foo} or @samp{bar},}
|
|
1887 ;; @r{using @code{foo-bar-face}, even if they have already been highlighted.}
|
|
1888 ;; @r{@code{foo-bar-face} should be a variable whose value is a face.}
|
|
1889 ("foo\\|bar" 0 foo-bar-face t)
|
|
1890
|
25751
|
1891 ;; @r{Highlight the first subexpression within each occurrence}
|
21007
|
1892 ;; @r{that the function @code{fubar-match} finds,}
|
|
1893 ;; @r{using the face which is the value of @code{fubar-face}.}
|
|
1894 (fubar-match 1 fubar-face)
|
|
1895 @end smallexample
|
|
1896
|
|
1897 @item (@var{matcher} @var{highlighters}@dots{})
|
|
1898 This sort of element specifies several @var{highlighter} lists for a
|
|
1899 single @var{matcher}. In order for this to be useful, each
|
|
1900 @var{highlighter} should have a different value of @var{subexp}; that is,
|
|
1901 each one should apply to a different subexpression of @var{matcher}.
|
|
1902
|
|
1903 @ignore
|
|
1904 @item (@var{matcher} . @var{anchored})
|
|
1905 In this kind of element, @var{anchored} acts much like a
|
|
1906 @var{highlighter}, but it is more complex and can specify multiple
|
|
1907 successive searches.
|
|
1908
|
|
1909 For highlighting single items, typically only @var{highlighter} is
|
|
1910 required. However, if an item or (typically) items are to be
|
|
1911 highlighted following the instance of another item (the anchor) then
|
|
1912 @var{anchored} may be required.
|
|
1913
|
|
1914 It has this format:
|
|
1915
|
|
1916 @example
|
|
1917 (@var{submatcher} @var{pre-match-form} @var{post-match-form} @var{highlighters}@dots{})
|
|
1918 @end example
|
|
1919
|
|
1920 @c I can't parse this text -- rms
|
|
1921 where @var{submatcher} is much like @var{matcher}, with one
|
|
1922 exception---see below. @var{pre-match-form} and @var{post-match-form}
|
|
1923 are evaluated before the first, and after the last, instance
|
|
1924 @var{anchored}'s @var{submatcher} is used. Therefore they can be used
|
22138
|
1925 to initialize before, and cleanup after, @var{submatcher} is used.
|
21007
|
1926 Typically, @var{pre-match-form} is used to move to some position
|
|
1927 relative to the original @var{submatcher}, before starting with
|
|
1928 @var{anchored}'s @var{submatcher}. @var{post-match-form} might be used
|
|
1929 to move, before resuming with @var{anchored}'s parent's @var{matcher}.
|
|
1930
|
|
1931 For example, an element of the form highlights (if not already highlighted):
|
|
1932
|
|
1933 @example
|
|
1934 ("\\<anchor\\>" (0 anchor-face) ("\\<item\\>" nil nil (0 item-face)))
|
|
1935 @end example
|
|
1936
|
|
1937 Discrete occurrences of @samp{anchor} in the value of
|
|
1938 @code{anchor-face}, and subsequent discrete occurrences of @samp{item}
|
|
1939 (on the same line) in the value of @code{item-face}. (Here
|
|
1940 @var{pre-match-form} and @var{post-match-form} are @code{nil}.
|
|
1941 Therefore @samp{item} is initially searched for starting from the end of
|
|
1942 the match of @samp{anchor}, and searching for subsequent instance of
|
|
1943 @samp{anchor} resumes from where searching for @samp{item} concluded.)
|
|
1944
|
|
1945 The above-mentioned exception is as follows. The limit of the
|
|
1946 @var{submatcher} search defaults to the end of the line after
|
|
1947 @var{pre-match-form} is evaluated. However, if @var{pre-match-form}
|
|
1948 returns a position greater than the position after @var{pre-match-form}
|
|
1949 is evaluated, that position is used as the limit of the search. It is
|
|
1950 generally a bad idea to return a position greater than the end of the
|
|
1951 line; in other words, the @var{submatcher} search should not span lines.
|
|
1952
|
|
1953 @item (@var{matcher} @var{highlighters-or-anchoreds} ...)
|
|
1954 @end ignore
|
|
1955
|
|
1956 @item (eval . @var{form})
|
21682
|
1957 Here @var{form} is an expression to be evaluated the first time
|
21007
|
1958 this value of @code{font-lock-keywords} is used in a buffer.
|
21682
|
1959 Its value should have one of the forms described in this table.
|
21007
|
1960 @end table
|
|
1961
|
|
1962 @strong{Warning:} Do not design an element of @code{font-lock-keywords}
|
|
1963 to match text which spans lines; this does not work reliably. While
|
|
1964 @code{font-lock-fontify-buffer} handles multi-line patterns correctly,
|
|
1965 updating when you edit the buffer does not, since it considers text one
|
|
1966 line at a time.
|
|
1967
|
|
1968 @node Other Font Lock Variables
|
|
1969 @subsection Other Font Lock Variables
|
|
1970
|
|
1971 This section describes additional variables that a major mode
|
|
1972 can set by means of @code{font-lock-defaults}.
|
|
1973
|
|
1974 @defvar font-lock-keywords-only
|
|
1975 Non-@code{nil} means Font Lock should not fontify comments or strings
|
21682
|
1976 syntactically; it should only fontify based on
|
|
1977 @code{font-lock-keywords}.
|
21007
|
1978 @end defvar
|
|
1979
|
|
1980 @ignore
|
22138
|
1981 Other variables include those for buffer-specialized fontification functions,
|
21007
|
1982 `font-lock-fontify-buffer-function', `font-lock-unfontify-buffer-function',
|
|
1983 `font-lock-fontify-region-function', `font-lock-unfontify-region-function',
|
|
1984 `font-lock-inhibit-thing-lock' and `font-lock-maximum-size'.
|
|
1985 @end ignore
|
|
1986
|
|
1987 @defvar font-lock-keywords-case-fold-search
|
21682
|
1988 Non-@code{nil} means that regular expression matching for the sake of
|
|
1989 @code{font-lock-keywords} should be case-insensitive.
|
|
1990 @end defvar
|
|
1991
|
|
1992 @defvar font-lock-syntax-table
|
|
1993 This variable specifies the syntax table to use for fontification of
|
|
1994 comments and strings.
|
21007
|
1995 @end defvar
|
|
1996
|
|
1997 @defvar font-lock-beginning-of-syntax-function
|
21682
|
1998 If this variable is non-@code{nil}, it should be a function to move
|
|
1999 point back to a position that is syntactically at ``top level'' and
|
|
2000 outside of strings or comments. Font Lock uses this when necessary
|
|
2001 to get the right results for syntactic fontification.
|
21007
|
2002
|
|
2003 This function is called with no arguments. It should leave point at the
|
|
2004 beginning of any enclosing syntactic block. Typical values are
|
|
2005 @code{beginning-of-line} (i.e., the start of the line is known to be
|
|
2006 outside a syntactic block), or @code{beginning-of-defun} for programming
|
|
2007 modes or @code{backward-paragraph} for textual modes (i.e., the
|
|
2008 mode-dependent function is known to move outside a syntactic block).
|
|
2009
|
|
2010 If the value is @code{nil}, the beginning of the buffer is used as a
|
21682
|
2011 position outside of a syntactic block. This cannot be wrong, but it can
|
|
2012 be slow.
|
21007
|
2013 @end defvar
|
|
2014
|
|
2015 @defvar font-lock-mark-block-function
|
21682
|
2016 If this variable is non-@code{nil}, it should be a function that is
|
|
2017 called with no arguments, to choose an enclosing range of text for
|
|
2018 refontification for the command @kbd{M-g M-g}
|
|
2019 (@code{font-lock-fontify-block}).
|
21007
|
2020
|
21682
|
2021 The function should report its choice by placing the region around it.
|
|
2022 A good choice is a range of text large enough to give proper results,
|
|
2023 but not too large so that refontification becomes slow. Typical values
|
|
2024 are @code{mark-defun} for programming modes or @code{mark-paragraph} for
|
|
2025 textual modes.
|
21007
|
2026 @end defvar
|
|
2027
|
|
2028 @node Levels of Font Lock
|
|
2029 @subsection Levels of Font Lock
|
|
2030
|
|
2031 Many major modes offer three different levels of fontification. You
|
|
2032 can define multiple levels by using a list of symbols for @var{keywords}
|
|
2033 in @code{font-lock-defaults}. Each symbol specifies one level of
|
|
2034 fontification; it is up to the user to choose one of these levels. The
|
|
2035 chosen level's symbol value is used to initialize
|
|
2036 @code{font-lock-keywords}.
|
|
2037
|
21682
|
2038 Here are the conventions for how to define the levels of
|
|
2039 fontification:
|
|
2040
|
21007
|
2041 @itemize @bullet
|
|
2042 @item
|
|
2043 Level 1: highlight function declarations, file directives (such as include or
|
|
2044 import directives), strings and comments. The idea is speed, so only
|
|
2045 the most important and top-level components are fontified.
|
|
2046
|
|
2047 @item
|
21682
|
2048 Level 2: in addition to level 1, highlight all language keywords,
|
|
2049 including type names that act like keywords, as well as named constant
|
|
2050 values. The idea is that all keywords (either syntactic or semantic)
|
|
2051 should be fontified appropriately.
|
21007
|
2052
|
|
2053 @item
|
21682
|
2054 Level 3: in addition to level 2, highlight the symbols being defined in
|
|
2055 function and variable declarations, and all builtin function names,
|
|
2056 wherever they appear.
|
21007
|
2057 @end itemize
|
|
2058
|
|
2059 @node Faces for Font Lock
|
|
2060 @subsection Faces for Font Lock
|
|
2061
|
|
2062 You can make Font Lock mode use any face, but several faces are
|
|
2063 defined specifically for Font Lock mode. Each of these symbols is both
|
|
2064 a face name, and a variable whose default value is the symbol itself.
|
|
2065 Thus, the default value of @code{font-lock-comment-face} is
|
|
2066 @code{font-lock-comment-face}. This means you can write
|
|
2067 @code{font-lock-comment-face} in a context such as
|
|
2068 @code{font-lock-keywords} where a face-name-valued expression is used.
|
|
2069
|
|
2070 @table @code
|
|
2071 @item font-lock-comment-face
|
|
2072 @vindex font-lock-comment-face
|
|
2073 Used (typically) for comments.
|
|
2074
|
|
2075 @item font-lock-string-face
|
|
2076 @vindex font-lock-string-face
|
|
2077 Used (typically) for string constants.
|
|
2078
|
|
2079 @item font-lock-keyword-face
|
|
2080 @vindex font-lock-keyword-face
|
|
2081 Used (typically) for keywords---names that have special syntactic
|
|
2082 significance, like @code{for} and @code{if} in C.
|
|
2083
|
|
2084 @item font-lock-builtin-face
|
|
2085 @vindex font-lock-builtin-face
|
|
2086 Used (typically) for built-in function names.
|
|
2087
|
|
2088 @item font-lock-function-name-face
|
|
2089 @vindex font-lock-function-name-face
|
|
2090 Used (typically) for the name of a function being defined or declared,
|
|
2091 in a function definition or declaration.
|
|
2092
|
|
2093 @item font-lock-variable-name-face
|
|
2094 @vindex font-lock-variable-name-face
|
|
2095 Used (typically) for the name of a variable being defined or declared,
|
|
2096 in a variable definition or declaration.
|
|
2097
|
|
2098 @item font-lock-type-face
|
|
2099 @vindex font-lock-type-face
|
|
2100 Used (typically) for names of user-defined data types,
|
|
2101 where they are defined and where they are used.
|
|
2102
|
|
2103 @item font-lock-constant-face
|
|
2104 @vindex font-lock-constant-face
|
|
2105 Used (typically) for constant names.
|
|
2106
|
|
2107 @item font-lock-warning-face
|
|
2108 @vindex font-lock-warning-face
|
|
2109 Used (typically) for constructs that are peculiar, or that greatly
|
|
2110 change the meaning of other text. For example, this is used for
|
|
2111 @samp{;;;###autoload} cookies in Emacs Lisp, and for @code{#error}
|
|
2112 directives in C.
|
|
2113 @end table
|
|
2114
|
21682
|
2115 @node Syntactic Font Lock
|
|
2116 @subsection Syntactic Font Lock
|
|
2117
|
|
2118 Font Lock mode can be used to update @code{syntax-table} properties
|
|
2119 automatically. This is useful in languages for which a single syntax
|
|
2120 table by itself is not sufficient.
|
|
2121
|
|
2122 @defvar font-lock-syntactic-keywords
|
|
2123 This variable enables and controls syntactic Font Lock. Its value
|
|
2124 should be a list of elements of this form:
|
|
2125
|
|
2126 @example
|
|
2127 (@var{matcher} @var{subexp} @var{syntax} @var{override} @var{laxmatch})
|
|
2128 @end example
|
|
2129
|
|
2130 The parts of this element have the same meanings as in the corresponding
|
|
2131 sort of element of @code{font-lock-keywords},
|
|
2132
|
|
2133 @example
|
|
2134 (@var{matcher} @var{subexp} @var{facename} @var{override} @var{laxmatch})
|
|
2135 @end example
|
|
2136
|
|
2137 However, instead of specifying the value @var{facename} to use for the
|
|
2138 @code{face} property, it specifies the value @var{syntax} to use for the
|
|
2139 @code{syntax-table} property. Here, @var{syntax} can be a variable
|
|
2140 whose value is a syntax table, a syntax entry of the form
|
|
2141 @code{(@var{syntax-code} . @var{matching-char})}, or an expression whose
|
|
2142 value is one of those two types.
|
|
2143 @end defvar
|
|
2144
|
6451
|
2145 @node Hooks
|
|
2146 @section Hooks
|
|
2147 @cindex hooks
|
|
2148
|
|
2149 A @dfn{hook} is a variable where you can store a function or functions
|
|
2150 to be called on a particular occasion by an existing program. Emacs
|
|
2151 provides hooks for the sake of customization. Most often, hooks are set
|
25875
|
2152 up in the init file (@pxref{Init File}), but Lisp programs can set them also.
|
6451
|
2153 @xref{Standard Hooks}, for a list of standard hook variables.
|
|
2154
|
21007
|
2155 @cindex normal hook
|
6451
|
2156 Most of the hooks in Emacs are @dfn{normal hooks}. These variables
|
16056
|
2157 contain lists of functions to be called with no arguments. When the
|
|
2158 hook name ends in @samp{-hook}, that tells you it is normal. We try to
|
|
2159 make all hooks normal, as much as possible, so that you can use them in
|
|
2160 a uniform way.
|
|
2161
|
|
2162 Every major mode function is supposed to run a normal hook called the
|
|
2163 @dfn{mode hook} as the last step of initialization. This makes it easy
|
|
2164 for a user to customize the behavior of the mode, by overriding the
|
21682
|
2165 buffer-local variable assignments already made by the mode. But hooks
|
|
2166 are used in other contexts too. For example, the hook
|
|
2167 @code{suspend-hook} runs just before Emacs suspends itself
|
|
2168 (@pxref{Suspending Emacs}).
|
6451
|
2169
|
|
2170 The recommended way to add a hook function to a normal hook is by
|
|
2171 calling @code{add-hook} (see below). The hook functions may be any of
|
|
2172 the valid kinds of functions that @code{funcall} accepts (@pxref{What Is
|
|
2173 a Function}). Most normal hook variables are initially void;
|
|
2174 @code{add-hook} knows how to deal with this.
|
|
2175
|
21007
|
2176 @cindex abnormal hook
|
16056
|
2177 If the hook variable's name does not end with @samp{-hook}, that
|
25875
|
2178 indicates it is probably an @dfn{abnormal hook}. Then you should look at its
|
16056
|
2179 documentation to see how to use the hook properly.
|
6451
|
2180
|
16056
|
2181 If the variable's name ends in @samp{-functions} or @samp{-hooks},
|
|
2182 then the value is a list of functions, but it is abnormal in that either
|
|
2183 these functions are called with arguments or their values are used in
|
|
2184 some way. You can use @code{add-hook} to add a function to the list,
|
|
2185 but you must take care in writing the function. (A few of these
|
|
2186 variables are actually normal hooks which were named before we
|
|
2187 established the convention of using @samp{-hook} for them.)
|
|
2188
|
|
2189 If the variable's name ends in @samp{-function}, then its value
|
|
2190 is just a single function, not a list of functions.
|
6451
|
2191
|
21682
|
2192 Here's an example that uses a mode hook to turn on Auto Fill mode when
|
|
2193 in Lisp Interaction mode:
|
6451
|
2194
|
|
2195 @example
|
|
2196 (add-hook 'lisp-interaction-mode-hook 'turn-on-auto-fill)
|
|
2197 @end example
|
|
2198
|
|
2199 At the appropriate time, Emacs uses the @code{run-hooks} function to
|
12098
|
2200 run particular hooks. This function calls the hook functions that have
|
|
2201 been added with @code{add-hook}.
|
6451
|
2202
|
25875
|
2203 @defun run-hooks &rest hookvars
|
6451
|
2204 This function takes one or more hook variable names as arguments, and
|
25875
|
2205 runs each hook in turn. Each argument should be a symbol that is a hook
|
|
2206 variable. These arguments are processed in the order specified.
|
6451
|
2207
|
|
2208 If a hook variable has a non-@code{nil} value, that value may be a
|
|
2209 function or a list of functions. If the value is a function (either a
|
21007
|
2210 lambda expression or a symbol with a function definition), it is called.
|
|
2211 If it is a list, the elements are called, in order. The hook functions
|
|
2212 are called with no arguments. Nowadays, storing a single function in
|
|
2213 the hook variable is semi-obsolete; you should always use a list of
|
|
2214 functions.
|
6451
|
2215
|
12098
|
2216 For example, here's how @code{emacs-lisp-mode} runs its mode hook:
|
6451
|
2217
|
|
2218 @example
|
|
2219 (run-hooks 'emacs-lisp-mode-hook)
|
|
2220 @end example
|
|
2221 @end defun
|
|
2222
|
22138
|
2223 @defun run-hook-with-args hook &rest args
|
|
2224 This function is the way to run an abnormal hook which passes arguments
|
|
2225 to the hook functions. It calls each of the hook functions, passing
|
|
2226 each of them the arguments @var{args}.
|
|
2227 @end defun
|
|
2228
|
|
2229 @defun run-hook-with-args-until-failure hook &rest args
|
|
2230 This function is the way to run an abnormal hook which passes arguments
|
|
2231 to the hook functions, and stops as soon as any hook function fails. It
|
|
2232 calls each of the hook functions, passing each of them the arguments
|
22252
|
2233 @var{args}, until some hook function returns @code{nil}. Then it stops,
|
25875
|
2234 and returns @code{nil} if some hook function returned @code{nil}.
|
|
2235 Otherwise it returns a non-@code{nil} value.
|
22138
|
2236 @end defun
|
|
2237
|
|
2238 @defun run-hook-with-args-until-success hook &rest args
|
|
2239 This function is the way to run an abnormal hook which passes arguments
|
|
2240 to the hook functions, and stops as soon as any hook function succeeds.
|
|
2241 It calls each of the hook functions, passing each of them the arguments
|
|
2242 @var{args}, until some hook function returns non-@code{nil}. Then it
|
22252
|
2243 stops, and returns whatever was returned by the last hook function
|
|
2244 that was called.
|
22138
|
2245 @end defun
|
|
2246
|
12067
|
2247 @defun add-hook hook function &optional append local
|
6451
|
2248 This function is the handy way to add function @var{function} to hook
|
7253
|
2249 variable @var{hook}. The argument @var{function} may be any valid Lisp
|
|
2250 function with the proper number of arguments. For example,
|
6451
|
2251
|
|
2252 @example
|
|
2253 (add-hook 'text-mode-hook 'my-text-hook-function)
|
|
2254 @end example
|
|
2255
|
|
2256 @noindent
|
|
2257 adds @code{my-text-hook-function} to the hook called @code{text-mode-hook}.
|
|
2258
|
7253
|
2259 You can use @code{add-hook} for abnormal hooks as well as for normal
|
|
2260 hooks.
|
|
2261
|
6451
|
2262 It is best to design your hook functions so that the order in which they
|
|
2263 are executed does not matter. Any dependence on the order is ``asking
|
|
2264 for trouble.'' However, the order is predictable: normally,
|
|
2265 @var{function} goes at the front of the hook list, so it will be
|
21682
|
2266 executed first (barring another @code{add-hook} call). If the optional
|
|
2267 argument @var{append} is non-@code{nil}, the new hook function goes at
|
|
2268 the end of the hook list and will be executed last.
|
6451
|
2269
|
12067
|
2270 If @var{local} is non-@code{nil}, that says to make the new hook
|
34016
|
2271 function buffer-local in the current buffer and automatically calls
|
|
2272 @code{make-local-hook} to make the hook itself buffer-local.
|
6451
|
2273 @end defun
|
8929
|
2274
|
12067
|
2275 @defun remove-hook hook function &optional local
|
|
2276 This function removes @var{function} from the hook variable @var{hook}.
|
|
2277
|
|
2278 If @var{local} is non-@code{nil}, that says to remove @var{function}
|
21682
|
2279 from the buffer-local hook list instead of from the global hook list.
|
|
2280 If the hook variable itself is not buffer-local, then the value of
|
|
2281 @var{local} makes no difference.
|
12067
|
2282 @end defun
|
8929
|
2283
|
12067
|
2284 @defun make-local-hook hook
|
21682
|
2285 This function makes the hook variable @code{hook} buffer-local in the
|
|
2286 current buffer. When a hook variable is buffer-local, it can have
|
|
2287 buffer-local and global hook functions, and @code{run-hooks} runs all of
|
|
2288 them.
|
8929
|
2289
|
25875
|
2290 This function works by adding @code{t} as an element of the buffer-local
|
|
2291 value. That serves as a flag to use the hook functions listed in the default
|
|
2292 value of the hook variable, as well as those listed in the buffer-local value.
|
21682
|
2293 Since @code{run-hooks} understands this flag, @code{make-local-hook}
|
|
2294 works with all normal hooks. It works for only some non-normal
|
|
2295 hooks---those whose callers have been updated to understand this meaning
|
|
2296 of @code{t}.
|
12234
|
2297
|
12067
|
2298 Do not use @code{make-local-variable} directly for hook variables; it is
|
|
2299 not sufficient.
|
|
2300 @end defun
|