Commit | Line | Data |
---|---|---|
b8d4c8d0 GM |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
3 | @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999, 2001, | |
5df4f04c | 4 | @c 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc. |
b8d4c8d0 | 5 | @c See the file elisp.texi for copying conditions. |
6336d8c3 | 6 | @setfilename ../../info/modes |
b8d4c8d0 GM |
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 | |
769741e3 SM |
23 | * Hooks:: How to use hooks; how to write code that provides hooks. |
24 | * Major Modes:: Defining major modes. | |
25 | * Minor Modes:: Defining minor modes. | |
26 | * Mode Line Format:: Customizing the text that appears in the mode line. | |
5dcb4c4e | 27 | * Imenu:: How a mode can provide a menu |
b8d4c8d0 | 28 | of definitions in the buffer. |
5dcb4c4e SM |
29 | * Font Lock Mode:: How modes can highlight text according to syntax. |
30 | * Auto-Indentation:: How to teach Emacs to indent for a major mode. | |
31 | * Desktop Save Mode:: How modes can have buffer state saved between | |
b8d4c8d0 GM |
32 | Emacs sessions. |
33 | @end menu | |
34 | ||
35 | @node Hooks | |
36 | @section Hooks | |
37 | @cindex hooks | |
38 | ||
39 | A @dfn{hook} is a variable where you can store a function or functions | |
40 | to be called on a particular occasion by an existing program. Emacs | |
41 | provides hooks for the sake of customization. Most often, hooks are set | |
42 | up in the init file (@pxref{Init File}), but Lisp programs can set them also. | |
43 | @xref{Standard Hooks}, for a list of standard hook variables. | |
44 | ||
45 | @cindex normal hook | |
46 | Most of the hooks in Emacs are @dfn{normal hooks}. These variables | |
47 | contain lists of functions to be called with no arguments. By | |
48 | convention, whenever the hook name ends in @samp{-hook}, that tells | |
49 | you it is normal. We try to make all hooks normal, as much as | |
50 | possible, so that you can use them in a uniform way. | |
51 | ||
52 | Every major mode function is supposed to run a normal hook called | |
53 | the @dfn{mode hook} as the one of the last steps of initialization. | |
54 | This makes it easy for a user to customize the behavior of the mode, | |
55 | by overriding the buffer-local variable assignments already made by | |
56 | the mode. Most minor mode functions also run a mode hook at the end. | |
57 | But hooks are used in other contexts too. For example, the hook | |
58 | @code{suspend-hook} runs just before Emacs suspends itself | |
59 | (@pxref{Suspending Emacs}). | |
60 | ||
61 | The recommended way to add a hook function to a normal hook is by | |
62 | calling @code{add-hook} (see below). The hook functions may be any of | |
63 | the valid kinds of functions that @code{funcall} accepts (@pxref{What | |
64 | Is a Function}). Most normal hook variables are initially void; | |
65 | @code{add-hook} knows how to deal with this. You can add hooks either | |
66 | globally or buffer-locally with @code{add-hook}. | |
67 | ||
68 | @cindex abnormal hook | |
69 | If the hook variable's name does not end with @samp{-hook}, that | |
70 | indicates it is probably an @dfn{abnormal hook}. That means the hook | |
71 | functions are called with arguments, or their return values are used | |
72 | in some way. The hook's documentation says how the functions are | |
73 | called. You can use @code{add-hook} to add a function to an abnormal | |
74 | hook, but you must write the function to follow the hook's calling | |
75 | convention. | |
76 | ||
77 | By convention, abnormal hook names end in @samp{-functions} or | |
78 | @samp{-hooks}. If the variable's name ends in @samp{-function}, then | |
79 | its value is just a single function, not a list of functions. | |
80 | ||
fd9a7a58 | 81 | @menu |
769741e3 SM |
82 | * Running Hooks:: How to run a hook. |
83 | * Setting Hooks:: How to put functions on a hook, or remove them. | |
fd9a7a58 | 84 | @end menu |
b8d4c8d0 | 85 | |
fd9a7a58 RS |
86 | @node Running Hooks |
87 | @subsection Running Hooks | |
b8d4c8d0 | 88 | |
fd9a7a58 RS |
89 | At the appropriate times, Emacs uses the @code{run-hooks} function |
90 | and the other functions below to run particular hooks. | |
b8d4c8d0 GM |
91 | |
92 | @defun run-hooks &rest hookvars | |
93 | This function takes one or more normal hook variable names as | |
94 | arguments, and runs each hook in turn. Each argument should be a | |
95 | symbol that is a normal hook variable. These arguments are processed | |
96 | in the order specified. | |
97 | ||
98 | If a hook variable has a non-@code{nil} value, that value should be a | |
99 | list of functions. @code{run-hooks} calls all the functions, one by | |
100 | one, with no arguments. | |
101 | ||
102 | The hook variable's value can also be a single function---either a | |
103 | lambda expression or a symbol with a function definition---which | |
104 | @code{run-hooks} calls. But this usage is obsolete. | |
105 | @end defun | |
106 | ||
107 | @defun run-hook-with-args hook &rest args | |
108 | This function is the way to run an abnormal hook and always call all | |
109 | of the hook functions. It calls each of the hook functions one by | |
110 | one, passing each of them the arguments @var{args}. | |
111 | @end defun | |
112 | ||
113 | @defun run-hook-with-args-until-failure hook &rest args | |
114 | This function is the way to run an abnormal hook until one of the hook | |
115 | functions fails. It calls each of the hook functions, passing each of | |
116 | them the arguments @var{args}, until some hook function returns | |
117 | @code{nil}. It then stops and returns @code{nil}. If none of the | |
118 | hook functions return @code{nil}, it returns a non-@code{nil} value. | |
119 | @end defun | |
120 | ||
121 | @defun run-hook-with-args-until-success hook &rest args | |
122 | This function is the way to run an abnormal hook until a hook function | |
123 | succeeds. It calls each of the hook functions, passing each of them | |
124 | the arguments @var{args}, until some hook function returns | |
125 | non-@code{nil}. Then it stops, and returns whatever was returned by | |
126 | the last hook function that was called. If all hook functions return | |
127 | @code{nil}, it returns @code{nil} as well. | |
128 | @end defun | |
129 | ||
fd9a7a58 RS |
130 | @node Setting Hooks |
131 | @subsection Setting Hooks | |
132 | ||
133 | Here's an example that uses a mode hook to turn on Auto Fill mode when | |
134 | in Lisp Interaction mode: | |
135 | ||
136 | @example | |
137 | (add-hook 'lisp-interaction-mode-hook 'turn-on-auto-fill) | |
138 | @end example | |
139 | ||
b8d4c8d0 GM |
140 | @defun add-hook hook function &optional append local |
141 | This function is the handy way to add function @var{function} to hook | |
142 | variable @var{hook}. You can use it for abnormal hooks as well as for | |
143 | normal hooks. @var{function} can be any Lisp function that can accept | |
144 | the proper number of arguments for @var{hook}. For example, | |
145 | ||
146 | @example | |
147 | (add-hook 'text-mode-hook 'my-text-hook-function) | |
148 | @end example | |
149 | ||
150 | @noindent | |
151 | adds @code{my-text-hook-function} to the hook called @code{text-mode-hook}. | |
152 | ||
153 | If @var{function} is already present in @var{hook} (comparing using | |
154 | @code{equal}), then @code{add-hook} does not add it a second time. | |
155 | ||
fd9a7a58 RS |
156 | If @var{function} has a non-@code{nil} property |
157 | @code{permanent-local-hook}, then @code{kill-all-local-variables} (or | |
158 | changing major modes) won't delete it from the hook variable's local | |
159 | value. | |
160 | ||
41633740 CY |
161 | It is best to design your hook functions so that the order in which |
162 | they are executed does not matter. Any dependence on the order is | |
163 | asking for trouble. However, the order is predictable: normally, | |
b8d4c8d0 | 164 | @var{function} goes at the front of the hook list, so it will be |
41633740 CY |
165 | executed first (barring another @code{add-hook} call). If the |
166 | optional argument @var{append} is non-@code{nil}, the new hook | |
167 | function goes at the end of the hook list and will be executed last. | |
b8d4c8d0 GM |
168 | |
169 | @code{add-hook} can handle the cases where @var{hook} is void or its | |
170 | value is a single function; it sets or changes the value to a list of | |
171 | functions. | |
172 | ||
173 | If @var{local} is non-@code{nil}, that says to add @var{function} to | |
174 | the buffer-local hook list instead of to the global hook list. If | |
175 | needed, this makes the hook buffer-local and adds @code{t} to the | |
176 | buffer-local value. The latter acts as a flag to run the hook | |
177 | functions in the default value as well as in the local value. | |
178 | @end defun | |
179 | ||
180 | @defun remove-hook hook function &optional local | |
181 | This function removes @var{function} from the hook variable | |
182 | @var{hook}. It compares @var{function} with elements of @var{hook} | |
183 | using @code{equal}, so it works for both symbols and lambda | |
184 | expressions. | |
185 | ||
186 | If @var{local} is non-@code{nil}, that says to remove @var{function} | |
187 | from the buffer-local hook list instead of from the global hook list. | |
188 | @end defun | |
189 | ||
190 | @node Major Modes | |
191 | @section Major Modes | |
192 | @cindex major mode | |
193 | ||
194 | Major modes specialize Emacs for editing particular kinds of text. | |
195 | Each buffer has only one major mode at a time. For each major mode | |
196 | there is a function to switch to that mode in the current buffer; its | |
197 | name should end in @samp{-mode}. These functions work by setting | |
198 | buffer-local variable bindings and other data associated with the | |
199 | buffer, such as a local keymap. The effect lasts until you switch | |
200 | to another major mode in the same buffer. | |
201 | ||
202 | @menu | |
769741e3 SM |
203 | * Major Mode Basics:: |
204 | * Major Mode Conventions:: Coding conventions for keymaps, etc. | |
205 | * Auto Major Mode:: How Emacs chooses the major mode automatically. | |
206 | * Mode Help:: Finding out how to use a mode. | |
207 | * Derived Modes:: Defining a new major mode based on another major | |
b8d4c8d0 | 208 | mode. |
769741e3 | 209 | * Generic Modes:: Defining a simple major mode that supports |
b8d4c8d0 | 210 | comment syntax and Font Lock mode. |
769741e3 SM |
211 | * Mode Hooks:: Hooks run at the end of major mode functions. |
212 | * Example Major Modes:: Text mode and Lisp modes. | |
b8d4c8d0 GM |
213 | @end menu |
214 | ||
215 | @node Major Mode Basics | |
216 | @subsection Major Mode Basics | |
217 | @cindex Fundamental mode | |
218 | ||
219 | The least specialized major mode is called @dfn{Fundamental mode}. | |
220 | This mode has no mode-specific definitions or variable settings, so each | |
221 | Emacs command behaves in its default manner, and each option is in its | |
222 | default state. All other major modes redefine various keys and options. | |
223 | For example, Lisp Interaction mode provides special key bindings for | |
224 | @kbd{C-j} (@code{eval-print-last-sexp}), @key{TAB} | |
225 | (@code{lisp-indent-line}), and other keys. | |
226 | ||
227 | When you need to write several editing commands to help you perform a | |
228 | specialized editing task, creating a new major mode is usually a good | |
229 | idea. In practice, writing a major mode is easy (in contrast to | |
230 | writing a minor mode, which is often difficult). | |
231 | ||
232 | If the new mode is similar to an old one, it is often unwise to | |
233 | modify the old one to serve two purposes, since it may become harder | |
234 | to use and maintain. Instead, copy and rename an existing major mode | |
41633740 CY |
235 | definition and alter the copy---or use the @code{define-derived-mode} |
236 | macro to define a @dfn{derived mode} (@pxref{Derived Modes}). For | |
237 | example, Rmail Edit mode is a major mode that is very similar to Text | |
238 | mode except that it provides two additional commands. Its definition | |
239 | is distinct from that of Text mode, but uses that of Text mode. | |
b8d4c8d0 GM |
240 | |
241 | Even if the new mode is not an obvious derivative of any other mode, | |
769741e3 SM |
242 | we recommend to use @code{define-derived-mode}, since it automatically |
243 | enforces the most important coding conventions for you. | |
b8d4c8d0 GM |
244 | |
245 | For a very simple programming language major mode that handles | |
246 | comments and fontification, you can use @code{define-generic-mode}. | |
247 | @xref{Generic Modes}. | |
248 | ||
249 | Rmail Edit mode offers an example of changing the major mode | |
250 | temporarily for a buffer, so it can be edited in a different way (with | |
251 | ordinary Emacs commands rather than Rmail commands). In such cases, the | |
252 | temporary major mode usually provides a command to switch back to the | |
253 | buffer's usual mode (Rmail mode, in this case). You might be tempted to | |
254 | present the temporary redefinitions inside a recursive edit and restore | |
255 | the usual ones when the user exits; but this is a bad idea because it | |
256 | constrains the user's options when it is done in more than one buffer: | |
257 | recursive edits must be exited most-recently-entered first. Using an | |
258 | alternative major mode avoids this limitation. @xref{Recursive | |
259 | Editing}. | |
260 | ||
261 | The standard GNU Emacs Lisp library directory tree contains the code | |
262 | for several major modes, in files such as @file{text-mode.el}, | |
263 | @file{texinfo.el}, @file{lisp-mode.el}, @file{c-mode.el}, and | |
264 | @file{rmail.el}. They are found in various subdirectories of the | |
265 | @file{lisp} directory. You can study these libraries to see how modes | |
266 | are written. Text mode is perhaps the simplest major mode aside from | |
267 | Fundamental mode. Rmail mode is a complicated and specialized mode. | |
268 | ||
269 | @node Major Mode Conventions | |
270 | @subsection Major Mode Conventions | |
271 | @cindex major mode conventions | |
272 | @cindex conventions for writing major modes | |
273 | ||
274 | The code for existing major modes follows various coding conventions, | |
275 | including conventions for local keymap and syntax table initialization, | |
276 | global names, and hooks. Please follow these conventions when you | |
277 | define a new major mode. (Fundamental mode is an exception to many | |
278 | of these conventions, because its definition is to present the global | |
279 | state of Emacs.) | |
280 | ||
281 | This list of conventions is only partial, because each major mode | |
282 | should aim for consistency in general with other Emacs major modes. | |
283 | This makes Emacs as a whole more coherent. It is impossible to list | |
284 | here all the possible points where this issue might come up; if the | |
285 | Emacs developers point out an area where your major mode deviates from | |
286 | the usual conventions, please make it compatible. | |
287 | ||
288 | @itemize @bullet | |
289 | @item | |
290 | Define a command whose name ends in @samp{-mode}, with no arguments, | |
291 | that switches to the new mode in the current buffer. This command | |
292 | should set up the keymap, syntax table, and buffer-local variables in an | |
293 | existing buffer, without changing the buffer's contents. | |
294 | ||
295 | @item | |
296 | Write a documentation string for this command that describes the | |
297 | special commands available in this mode. @kbd{C-h m} | |
298 | (@code{describe-mode}) in your mode will display this string. | |
299 | ||
300 | The documentation string may include the special documentation | |
301 | substrings, @samp{\[@var{command}]}, @samp{\@{@var{keymap}@}}, and | |
302 | @samp{\<@var{keymap}>}, which enable the documentation to adapt | |
303 | automatically to the user's own key bindings. @xref{Keys in | |
304 | Documentation}. | |
305 | ||
306 | @item | |
307 | The major mode command should start by calling | |
308 | @code{kill-all-local-variables}. This runs the normal hook | |
309 | @code{change-major-mode-hook}, then gets rid of the buffer-local | |
310 | variables of the major mode previously in effect. @xref{Creating | |
311 | Buffer-Local}. | |
312 | ||
313 | @item | |
314 | The major mode command should set the variable @code{major-mode} to the | |
315 | major mode command symbol. This is how @code{describe-mode} discovers | |
316 | which documentation to print. | |
317 | ||
318 | @item | |
319 | The major mode command should set the variable @code{mode-name} to the | |
9cf52b11 EZ |
320 | ``pretty'' name of the mode, usually a string (but see @ref{Mode Line |
321 | Data}, for other possible forms). The name of the mode appears | |
322 | in the mode line. | |
b8d4c8d0 GM |
323 | |
324 | @item | |
325 | @cindex functions in modes | |
326 | Since all global names are in the same name space, all the global | |
327 | variables, constants, and functions that are part of the mode should | |
328 | have names that start with the major mode name (or with an abbreviation | |
329 | of it if the name is long). @xref{Coding Conventions}. | |
330 | ||
331 | @item | |
332 | In a major mode for editing some kind of structured text, such as a | |
333 | programming language, indentation of text according to structure is | |
334 | probably useful. So the mode should set @code{indent-line-function} | |
335 | to a suitable function, and probably customize other variables | |
5dcb4c4e | 336 | for indentation. @xref{Auto-Indentation}. |
b8d4c8d0 GM |
337 | |
338 | @item | |
339 | @cindex keymaps in modes | |
340 | The major mode should usually have its own keymap, which is used as the | |
341 | local keymap in all buffers in that mode. The major mode command should | |
342 | call @code{use-local-map} to install this local map. @xref{Active | |
343 | Keymaps}, for more information. | |
344 | ||
345 | This keymap should be stored permanently in a global variable named | |
346 | @code{@var{modename}-mode-map}. Normally the library that defines the | |
347 | mode sets this variable. | |
348 | ||
349 | @xref{Tips for Defining}, for advice about how to write the code to set | |
350 | up the mode's keymap variable. | |
351 | ||
352 | @item | |
353 | The key sequences bound in a major mode keymap should usually start with | |
354 | @kbd{C-c}, followed by a control character, a digit, or @kbd{@{}, | |
355 | @kbd{@}}, @kbd{<}, @kbd{>}, @kbd{:} or @kbd{;}. The other punctuation | |
356 | characters are reserved for minor modes, and ordinary letters are | |
357 | reserved for users. | |
358 | ||
359 | A major mode can also rebind the keys @kbd{M-n}, @kbd{M-p} and | |
360 | @kbd{M-s}. The bindings for @kbd{M-n} and @kbd{M-p} should normally | |
361 | be some kind of ``moving forward and backward,'' but this does not | |
362 | necessarily mean cursor motion. | |
363 | ||
364 | It is legitimate for a major mode to rebind a standard key sequence if | |
365 | it provides a command that does ``the same job'' in a way better | |
366 | suited to the text this mode is used for. For example, a major mode | |
367 | for editing a programming language might redefine @kbd{C-M-a} to | |
368 | ``move to the beginning of a function'' in a way that works better for | |
369 | that language. | |
370 | ||
371 | It is also legitimate for a major mode to rebind a standard key | |
372 | sequence whose standard meaning is rarely useful in that mode. For | |
373 | instance, minibuffer modes rebind @kbd{M-r}, whose standard meaning is | |
374 | rarely of any use in the minibuffer. Major modes such as Dired or | |
375 | Rmail that do not allow self-insertion of text can reasonably redefine | |
376 | letters and other printing characters as special commands. | |
377 | ||
378 | @item | |
867d4bb3 | 379 | Major modes for editing text should not define @key{RET} to do |
b8d4c8d0 GM |
380 | anything other than insert a newline. However, it is ok for |
381 | specialized modes for text that users don't directly edit, such as | |
382 | Dired and Info modes, to redefine @key{RET} to do something entirely | |
383 | different. | |
384 | ||
385 | @item | |
386 | Major modes should not alter options that are primarily a matter of user | |
387 | preference, such as whether Auto-Fill mode is enabled. Leave this to | |
388 | each user to decide. However, a major mode should customize other | |
389 | variables so that Auto-Fill mode will work usefully @emph{if} the user | |
390 | decides to use it. | |
391 | ||
392 | @item | |
393 | @cindex syntax tables in modes | |
394 | The mode may have its own syntax table or may share one with other | |
395 | related modes. If it has its own syntax table, it should store this in | |
396 | a variable named @code{@var{modename}-mode-syntax-table}. @xref{Syntax | |
397 | Tables}. | |
398 | ||
399 | @item | |
400 | If the mode handles a language that has a syntax for comments, it should | |
401 | set the variables that define the comment syntax. @xref{Options for | |
402 | Comments,, Options Controlling Comments, emacs, The GNU Emacs Manual}. | |
403 | ||
404 | @item | |
405 | @cindex abbrev tables in modes | |
406 | The mode may have its own abbrev table or may share one with other | |
407 | related modes. If it has its own abbrev table, it should store this | |
408 | in a variable named @code{@var{modename}-mode-abbrev-table}. If the | |
409 | major mode command defines any abbrevs itself, it should pass @code{t} | |
410 | for the @var{system-flag} argument to @code{define-abbrev}. | |
411 | @xref{Defining Abbrevs}. | |
412 | ||
413 | @item | |
414 | The mode should specify how to do highlighting for Font Lock mode, by | |
415 | setting up a buffer-local value for the variable | |
416 | @code{font-lock-defaults} (@pxref{Font Lock Mode}). | |
417 | ||
418 | @item | |
419 | The mode should specify how Imenu should find the definitions or | |
420 | sections of a buffer, by setting up a buffer-local value for the | |
421 | variable @code{imenu-generic-expression}, for the two variables | |
422 | @code{imenu-prev-index-position-function} and | |
423 | @code{imenu-extract-index-name-function}, or for the variable | |
424 | @code{imenu-create-index-function} (@pxref{Imenu}). | |
425 | ||
426 | @item | |
427 | The mode can specify a local value for | |
428 | @code{eldoc-documentation-function} to tell ElDoc mode how to handle | |
429 | this mode. | |
430 | ||
769741e3 SM |
431 | @item |
432 | The mode can specify how to complete various keywords by adding | |
433 | to the special hook @code{completion-at-point-functions}. | |
434 | ||
b8d4c8d0 GM |
435 | @item |
436 | Use @code{defvar} or @code{defcustom} to set mode-related variables, so | |
437 | that they are not reinitialized if they already have a value. (Such | |
438 | reinitialization could discard customizations made by the user.) | |
439 | ||
440 | @item | |
441 | @cindex buffer-local variables in modes | |
442 | To make a buffer-local binding for an Emacs customization variable, use | |
443 | @code{make-local-variable} in the major mode command, not | |
444 | @code{make-variable-buffer-local}. The latter function would make the | |
445 | variable local to every buffer in which it is subsequently set, which | |
446 | would affect buffers that do not use this mode. It is undesirable for a | |
447 | mode to have such global effects. @xref{Buffer-Local Variables}. | |
448 | ||
449 | With rare exceptions, the only reasonable way to use | |
450 | @code{make-variable-buffer-local} in a Lisp package is for a variable | |
451 | which is used only within that package. Using it on a variable used by | |
452 | other packages would interfere with them. | |
453 | ||
454 | @item | |
455 | @cindex mode hook | |
456 | @cindex major mode hook | |
457 | Each major mode should have a normal @dfn{mode hook} named | |
458 | @code{@var{modename}-mode-hook}. The very last thing the major mode command | |
459 | should do is to call @code{run-mode-hooks}. This runs the mode hook, | |
460 | and then runs the normal hook @code{after-change-major-mode-hook}. | |
461 | @xref{Mode Hooks}. | |
462 | ||
463 | @item | |
464 | The major mode command may start by calling some other major mode | |
465 | command (called the @dfn{parent mode}) and then alter some of its | |
466 | settings. A mode that does this is called a @dfn{derived mode}. The | |
41633740 CY |
467 | recommended way to define one is to use the @code{define-derived-mode} |
468 | macro, but this is not required. Such a mode should call the parent | |
469 | mode command inside a @code{delay-mode-hooks} form. (Using | |
b8d4c8d0 GM |
470 | @code{define-derived-mode} does this automatically.) @xref{Derived |
471 | Modes}, and @ref{Mode Hooks}. | |
472 | ||
473 | @item | |
474 | If something special should be done if the user switches a buffer from | |
475 | this mode to any other major mode, this mode can set up a buffer-local | |
476 | value for @code{change-major-mode-hook} (@pxref{Creating Buffer-Local}). | |
477 | ||
478 | @item | |
479 | If this mode is appropriate only for specially-prepared text, then the | |
480 | major mode command symbol should have a property named @code{mode-class} | |
481 | with value @code{special}, put on as follows: | |
482 | ||
483 | @kindex mode-class @r{(property)} | |
484 | @cindex @code{special} | |
485 | @example | |
486 | (put 'funny-mode 'mode-class 'special) | |
487 | @end example | |
488 | ||
489 | @noindent | |
490 | This tells Emacs that new buffers created while the current buffer is | |
4e3b4528 SM |
491 | in Funny mode should not inherit Funny mode, in case the default value |
492 | of @code{major-mode} is @code{nil}. Modes such as Dired, Rmail, | |
b8d4c8d0 GM |
493 | and Buffer List use this feature. |
494 | ||
41633740 CY |
495 | The @code{define-derived-mode} macro automatically marks the derived |
496 | mode as special if the parent mode is special. The special mode | |
497 | @code{special-mode} provides a convenient parent for other special | |
498 | modes to inherit from; it sets @code{buffer-read-only} to @code{t}, | |
769741e3 | 499 | and does little else. |
41633740 | 500 | |
b8d4c8d0 GM |
501 | @item |
502 | If you want to make the new mode the default for files with certain | |
503 | recognizable names, add an element to @code{auto-mode-alist} to select | |
504 | the mode for those file names (@pxref{Auto Major Mode}). If you | |
505 | define the mode command to autoload, you should add this element in | |
506 | the same file that calls @code{autoload}. If you use an autoload | |
507 | cookie for the mode command, you can also use an autoload cookie for | |
508 | the form that adds the element (@pxref{autoload cookie}). If you do | |
509 | not autoload the mode command, it is sufficient to add the element in | |
510 | the file that contains the mode definition. | |
511 | ||
512 | @item | |
513 | In the comments that document the file, you should provide a sample | |
514 | @code{autoload} form and an example of how to add to | |
515 | @code{auto-mode-alist}, that users can include in their init files | |
516 | (@pxref{Init File}). | |
517 | ||
518 | @item | |
519 | @cindex mode loading | |
520 | The top-level forms in the file defining the mode should be written so | |
521 | that they may be evaluated more than once without adverse consequences. | |
522 | Even if you never load the file more than once, someone else will. | |
523 | @end itemize | |
524 | ||
525 | @node Auto Major Mode | |
526 | @subsection How Emacs Chooses a Major Mode | |
527 | @cindex major mode, automatic selection | |
528 | ||
529 | Based on information in the file name or in the file itself, Emacs | |
530 | automatically selects a major mode for the new buffer when a file is | |
531 | visited. It also processes local variables specified in the file text. | |
532 | ||
533 | @deffn Command fundamental-mode | |
534 | Fundamental mode is a major mode that is not specialized for anything | |
535 | in particular. Other major modes are defined in effect by comparison | |
536 | with this one---their definitions say what to change, starting from | |
537 | Fundamental mode. The @code{fundamental-mode} function does @emph{not} | |
538 | run any mode hooks; you're not supposed to customize it. (If you want Emacs | |
539 | to behave differently in Fundamental mode, change the @emph{global} | |
540 | state of Emacs.) | |
541 | @end deffn | |
542 | ||
543 | @deffn Command normal-mode &optional find-file | |
544 | This function establishes the proper major mode and buffer-local variable | |
545 | bindings for the current buffer. First it calls @code{set-auto-mode} | |
546 | (see below), then it runs @code{hack-local-variables} to parse, and | |
547 | bind or evaluate as appropriate, the file's local variables | |
548 | (@pxref{File Local Variables}). | |
549 | ||
550 | If the @var{find-file} argument to @code{normal-mode} is non-@code{nil}, | |
551 | @code{normal-mode} assumes that the @code{find-file} function is calling | |
552 | it. In this case, it may process local variables in the @samp{-*-} | |
553 | line or at the end of the file. The variable | |
554 | @code{enable-local-variables} controls whether to do so. @xref{File | |
555 | Variables, , Local Variables in Files, emacs, The GNU Emacs Manual}, | |
556 | for the syntax of the local variables section of a file. | |
557 | ||
558 | If you run @code{normal-mode} interactively, the argument | |
559 | @var{find-file} is normally @code{nil}. In this case, | |
560 | @code{normal-mode} unconditionally processes any file local variables. | |
561 | ||
562 | If @code{normal-mode} processes the local variables list and this list | |
563 | specifies a major mode, that mode overrides any mode chosen by | |
564 | @code{set-auto-mode}. If neither @code{set-auto-mode} nor | |
565 | @code{hack-local-variables} specify a major mode, the buffer stays in | |
4e3b4528 SM |
566 | the major mode determined by the default value of @code{major-mode} |
567 | (see below). | |
b8d4c8d0 GM |
568 | |
569 | @cindex file mode specification error | |
570 | @code{normal-mode} uses @code{condition-case} around the call to the | |
571 | major mode function, so errors are caught and reported as a @samp{File | |
572 | mode specification error}, followed by the original error message. | |
573 | @end deffn | |
574 | ||
575 | @defun set-auto-mode &optional keep-mode-if-same | |
576 | @cindex visited file mode | |
577 | This function selects the major mode that is appropriate for the | |
578 | current buffer. It bases its decision (in order of precedence) on | |
579 | the @w{@samp{-*-}} line, on the @w{@samp{#!}} line (using | |
580 | @code{interpreter-mode-alist}), on the text at the beginning of the | |
581 | buffer (using @code{magic-mode-alist}), and finally on the visited | |
582 | file name (using @code{auto-mode-alist}). @xref{Choosing Modes, , How | |
583 | Major Modes are Chosen, emacs, The GNU Emacs Manual}. However, this | |
584 | function does not look for the @samp{mode:} local variable near the | |
585 | end of a file; the @code{hack-local-variables} function does that. | |
586 | If @code{enable-local-variables} is @code{nil}, @code{set-auto-mode} | |
587 | does not check the @w{@samp{-*-}} line for a mode tag either. | |
588 | ||
589 | If @var{keep-mode-if-same} is non-@code{nil}, this function does not | |
590 | call the mode command if the buffer is already in the proper major | |
591 | mode. For instance, @code{set-visited-file-name} sets this to | |
592 | @code{t} to avoid killing buffer local variables that the user may | |
593 | have set. | |
594 | @end defun | |
595 | ||
4e3b4528 SM |
596 | @defopt major-mode |
597 | The buffer-local value of this variable holds the major mode | |
598 | currently active. The default value of this variable holds the | |
599 | default major mode for new buffers. The standard default value is | |
600 | @code{fundamental-mode}. | |
b8d4c8d0 | 601 | |
4e3b4528 | 602 | If the default value of @code{major-mode} is @code{nil}, Emacs uses |
b8d4c8d0 GM |
603 | the (previously) current buffer's major mode as the default major mode |
604 | of a new buffer. However, if that major mode symbol has a @code{mode-class} | |
605 | property with value @code{special}, then it is not used for new buffers; | |
606 | Fundamental mode is used instead. The modes that have this property are | |
607 | those such as Dired and Rmail that are useful only with text that has | |
608 | been specially prepared. | |
609 | @end defopt | |
610 | ||
611 | @defun set-buffer-major-mode buffer | |
4e3b4528 SM |
612 | This function sets the major mode of @var{buffer} to the default value of |
613 | @code{major-mode}; if that is @code{nil}, it uses the | |
b8d4c8d0 GM |
614 | current buffer's major mode (if that is suitable). As an exception, |
615 | if @var{buffer}'s name is @samp{*scratch*}, it sets the mode to | |
616 | @code{initial-major-mode}. | |
617 | ||
618 | The low-level primitives for creating buffers do not use this function, | |
619 | but medium-level commands such as @code{switch-to-buffer} and | |
620 | @code{find-file-noselect} use it whenever they create buffers. | |
621 | @end defun | |
622 | ||
623 | @defopt initial-major-mode | |
624 | @cindex @samp{*scratch*} | |
625 | The value of this variable determines the major mode of the initial | |
626 | @samp{*scratch*} buffer. The value should be a symbol that is a major | |
627 | mode command. The default value is @code{lisp-interaction-mode}. | |
628 | @end defopt | |
629 | ||
630 | @defvar interpreter-mode-alist | |
631 | This variable specifies major modes to use for scripts that specify a | |
632 | command interpreter in a @samp{#!} line. Its value is an alist with | |
633 | elements of the form @code{(@var{interpreter} . @var{mode})}; for | |
634 | example, @code{("perl" . perl-mode)} is one element present by | |
635 | default. The element says to use mode @var{mode} if the file | |
636 | specifies an interpreter which matches @var{interpreter}. | |
637 | @end defvar | |
638 | ||
639 | @defvar magic-mode-alist | |
640 | This variable's value is an alist with elements of the form | |
641 | @code{(@var{regexp} . @var{function})}, where @var{regexp} is a | |
642 | regular expression and @var{function} is a function or @code{nil}. | |
643 | After visiting a file, @code{set-auto-mode} calls @var{function} if | |
644 | the text at the beginning of the buffer matches @var{regexp} and | |
645 | @var{function} is non-@code{nil}; if @var{function} is @code{nil}, | |
646 | @code{auto-mode-alist} gets to decide the mode. | |
647 | @end defvar | |
648 | ||
649 | @defvar magic-fallback-mode-alist | |
650 | This works like @code{magic-mode-alist}, except that it is handled | |
651 | only if @code{auto-mode-alist} does not specify a mode for this file. | |
652 | @end defvar | |
653 | ||
654 | @defvar auto-mode-alist | |
655 | This variable contains an association list of file name patterns | |
656 | (regular expressions) and corresponding major mode commands. Usually, | |
657 | the file name patterns test for suffixes, such as @samp{.el} and | |
658 | @samp{.c}, but this need not be the case. An ordinary element of the | |
659 | alist looks like @code{(@var{regexp} . @var{mode-function})}. | |
660 | ||
661 | For example, | |
662 | ||
663 | @smallexample | |
664 | @group | |
665 | (("\\`/tmp/fol/" . text-mode) | |
666 | ("\\.texinfo\\'" . texinfo-mode) | |
667 | ("\\.texi\\'" . texinfo-mode) | |
668 | @end group | |
669 | @group | |
670 | ("\\.el\\'" . emacs-lisp-mode) | |
671 | ("\\.c\\'" . c-mode) | |
672 | ("\\.h\\'" . c-mode) | |
673 | @dots{}) | |
674 | @end group | |
675 | @end smallexample | |
676 | ||
677 | When you visit a file whose expanded file name (@pxref{File Name | |
678 | Expansion}), with version numbers and backup suffixes removed using | |
679 | @code{file-name-sans-versions} (@pxref{File Name Components}), matches | |
680 | a @var{regexp}, @code{set-auto-mode} calls the corresponding | |
681 | @var{mode-function}. This feature enables Emacs to select the proper | |
682 | major mode for most files. | |
683 | ||
684 | If an element of @code{auto-mode-alist} has the form @code{(@var{regexp} | |
685 | @var{function} t)}, then after calling @var{function}, Emacs searches | |
686 | @code{auto-mode-alist} again for a match against the portion of the file | |
687 | name that did not match before. This feature is useful for | |
688 | uncompression packages: an entry of the form @code{("\\.gz\\'" | |
689 | @var{function} t)} can uncompress the file and then put the uncompressed | |
690 | file in the proper mode according to the name sans @samp{.gz}. | |
691 | ||
692 | Here is an example of how to prepend several pattern pairs to | |
693 | @code{auto-mode-alist}. (You might use this sort of expression in your | |
694 | init file.) | |
695 | ||
696 | @smallexample | |
697 | @group | |
698 | (setq auto-mode-alist | |
699 | (append | |
700 | ;; @r{File name (within directory) starts with a dot.} | |
701 | '(("/\\.[^/]*\\'" . fundamental-mode) | |
702 | ;; @r{File name has no dot.} | |
2674569b | 703 | ("/[^\\./]*\\'" . fundamental-mode) |
b8d4c8d0 GM |
704 | ;; @r{File name ends in @samp{.C}.} |
705 | ("\\.C\\'" . c++-mode)) | |
706 | auto-mode-alist)) | |
707 | @end group | |
708 | @end smallexample | |
709 | @end defvar | |
710 | ||
711 | @node Mode Help | |
712 | @subsection Getting Help about a Major Mode | |
713 | @cindex mode help | |
714 | @cindex help for major mode | |
715 | @cindex documentation for major mode | |
716 | ||
717 | The @code{describe-mode} function is used to provide information | |
718 | about major modes. It is normally called with @kbd{C-h m}. The | |
719 | @code{describe-mode} function uses the value of @code{major-mode}, | |
720 | which is why every major mode function needs to set the | |
721 | @code{major-mode} variable. | |
722 | ||
723 | @deffn Command describe-mode | |
724 | This function displays the documentation of the current major mode. | |
725 | ||
726 | The @code{describe-mode} function calls the @code{documentation} | |
727 | function using the value of @code{major-mode} as an argument. Thus, it | |
728 | displays the documentation string of the major mode function. | |
729 | (@xref{Accessing Documentation}.) | |
730 | @end deffn | |
731 | ||
732 | @defvar major-mode | |
733 | This buffer-local variable holds the symbol for the current buffer's | |
734 | major mode. This symbol should have a function definition that is the | |
735 | command to switch to that major mode. The @code{describe-mode} | |
736 | function uses the documentation string of the function as the | |
737 | documentation of the major mode. | |
738 | @end defvar | |
739 | ||
740 | @node Derived Modes | |
741 | @subsection Defining Derived Modes | |
742 | @cindex derived mode | |
743 | ||
769741e3 SM |
744 | The recommended way to define a new major mode is to derive it |
745 | from an existing one using @code{define-derived-mode}. If there is no | |
746 | closely related mode, you can inherit from @code{text-mode}, | |
747 | @code{special-mode}, or in the worst case @code{fundamental-mode}. | |
b8d4c8d0 GM |
748 | |
749 | @defmac define-derived-mode variant parent name docstring keyword-args@dots{} body@dots{} | |
c986813b | 750 | This macro defines @var{variant} as a major mode command, using |
b8d4c8d0 GM |
751 | @var{name} as the string form of the mode name. @var{variant} and |
752 | @var{parent} should be unquoted symbols. | |
753 | ||
754 | The new command @var{variant} is defined to call the function | |
755 | @var{parent}, then override certain aspects of that parent mode: | |
756 | ||
757 | @itemize @bullet | |
758 | @item | |
759 | The new mode has its own sparse keymap, named | |
760 | @code{@var{variant}-map}. @code{define-derived-mode} | |
761 | makes the parent mode's keymap the parent of the new map, unless | |
762 | @code{@var{variant}-map} is already set and already has a parent. | |
763 | ||
764 | @item | |
765 | The new mode has its own syntax table, kept in the variable | |
766 | @code{@var{variant}-syntax-table}, unless you override this using the | |
767 | @code{:syntax-table} keyword (see below). @code{define-derived-mode} | |
768 | makes the parent mode's syntax-table the parent of | |
769 | @code{@var{variant}-syntax-table}, unless the latter is already set | |
770 | and already has a parent different from the standard syntax table. | |
771 | ||
772 | @item | |
773 | The new mode has its own abbrev table, kept in the variable | |
774 | @code{@var{variant}-abbrev-table}, unless you override this using the | |
775 | @code{:abbrev-table} keyword (see below). | |
776 | ||
777 | @item | |
778 | The new mode has its own mode hook, @code{@var{variant}-hook}. It | |
779 | runs this hook, after running the hooks of its ancestor modes, with | |
780 | @code{run-mode-hooks}, as the last thing it does. @xref{Mode Hooks}. | |
781 | @end itemize | |
782 | ||
783 | In addition, you can specify how to override other aspects of | |
784 | @var{parent} with @var{body}. The command @var{variant} | |
785 | evaluates the forms in @var{body} after setting up all its usual | |
786 | overrides, just before running the mode hooks. | |
787 | ||
c986813b CY |
788 | If @var{parent} has a non-@code{nil} @code{mode-class} symbol |
789 | property, then @code{define-derived-mode} sets the @code{mode-class} | |
790 | property of @var{variant} to the same value. This ensures, for | |
791 | example, that if @var{parent} is a special mode, then @var{variant} is | |
792 | also a special mode (@pxref{Major Mode Conventions}). | |
793 | ||
b8d4c8d0 GM |
794 | You can also specify @code{nil} for @var{parent}. This gives the new |
795 | mode no parent. Then @code{define-derived-mode} behaves as described | |
796 | above, but, of course, omits all actions connected with @var{parent}. | |
797 | ||
798 | The argument @var{docstring} specifies the documentation string for | |
799 | the new mode. @code{define-derived-mode} adds some general | |
800 | information about the mode's hook, followed by the mode's keymap, at | |
801 | the end of this docstring. If you omit @var{docstring}, | |
802 | @code{define-derived-mode} generates a documentation string. | |
803 | ||
804 | The @var{keyword-args} are pairs of keywords and values. The values | |
805 | are evaluated. The following keywords are currently supported: | |
806 | ||
807 | @table @code | |
808 | @item :syntax-table | |
809 | You can use this to explicitly specify a syntax table for the new | |
810 | mode. If you specify a @code{nil} value, the new mode uses the same | |
811 | syntax table as @var{parent}, or the standard syntax table if | |
812 | @var{parent} is @code{nil}. (Note that this does @emph{not} follow | |
813 | the convention used for non-keyword arguments that a @code{nil} value | |
814 | is equivalent with not specifying the argument.) | |
815 | ||
816 | @item :abbrev-table | |
817 | You can use this to explicitly specify an abbrev table for the new | |
818 | mode. If you specify a @code{nil} value, the new mode uses the same | |
819 | abbrev table as @var{parent}, or @code{fundamental-mode-abbrev-table} | |
820 | if @var{parent} is @code{nil}. (Again, a @code{nil} value is | |
821 | @emph{not} equivalent to not specifying this keyword.) | |
822 | ||
823 | @item :group | |
824 | If this is specified, the value should be the customization group for | |
825 | this mode. (Not all major modes have one.) Only the (still | |
826 | experimental and unadvertised) command @code{customize-mode} currently | |
827 | uses this. @code{define-derived-mode} does @emph{not} automatically | |
828 | define the specified customization group. | |
829 | @end table | |
830 | ||
831 | Here is a hypothetical example: | |
832 | ||
833 | @example | |
834 | (define-derived-mode hypertext-mode | |
835 | text-mode "Hypertext" | |
836 | "Major mode for hypertext. | |
837 | \\@{hypertext-mode-map@}" | |
838 | (setq case-fold-search nil)) | |
839 | ||
840 | (define-key hypertext-mode-map | |
841 | [down-mouse-3] 'do-hyper-link) | |
842 | @end example | |
843 | ||
844 | Do not write an @code{interactive} spec in the definition; | |
845 | @code{define-derived-mode} does that automatically. | |
846 | @end defmac | |
847 | ||
848 | @node Generic Modes | |
849 | @subsection Generic Modes | |
850 | @cindex generic mode | |
851 | ||
852 | @dfn{Generic modes} are simple major modes with basic support for | |
853 | comment syntax and Font Lock mode. To define a generic mode, use the | |
854 | macro @code{define-generic-mode}. See the file @file{generic-x.el} | |
855 | for some examples of the use of @code{define-generic-mode}. | |
856 | ||
857 | @defmac define-generic-mode mode comment-list keyword-list font-lock-list auto-mode-list function-list &optional docstring | |
858 | This macro defines a generic mode command named @var{mode} (a symbol, | |
859 | not quoted). The optional argument @var{docstring} is the | |
860 | documentation for the mode command. If you do not supply it, | |
861 | @code{define-generic-mode} generates one by default. | |
862 | ||
863 | The argument @var{comment-list} is a list in which each element is | |
864 | either a character, a string of one or two characters, or a cons cell. | |
865 | A character or a string is set up in the mode's syntax table as a | |
866 | ``comment starter.'' If the entry is a cons cell, the @sc{car} is set | |
867 | up as a ``comment starter'' and the @sc{cdr} as a ``comment ender.'' | |
868 | (Use @code{nil} for the latter if you want comments to end at the end | |
869 | of the line.) Note that the syntax table mechanism has limitations | |
870 | about what comment starters and enders are actually possible. | |
871 | @xref{Syntax Tables}. | |
872 | ||
873 | The argument @var{keyword-list} is a list of keywords to highlight | |
874 | with @code{font-lock-keyword-face}. Each keyword should be a string. | |
875 | Meanwhile, @var{font-lock-list} is a list of additional expressions to | |
876 | highlight. Each element of this list should have the same form as an | |
877 | element of @code{font-lock-keywords}. @xref{Search-based | |
878 | Fontification}. | |
879 | ||
880 | The argument @var{auto-mode-list} is a list of regular expressions to | |
881 | add to the variable @code{auto-mode-alist}. They are added by the execution | |
882 | of the @code{define-generic-mode} form, not by expanding the macro call. | |
883 | ||
884 | Finally, @var{function-list} is a list of functions for the mode | |
885 | command to call for additional setup. It calls these functions just | |
886 | before it runs the mode hook variable @code{@var{mode}-hook}. | |
887 | @end defmac | |
888 | ||
889 | @node Mode Hooks | |
890 | @subsection Mode Hooks | |
891 | ||
892 | Every major mode function should finish by running its mode hook and | |
893 | the mode-independent normal hook @code{after-change-major-mode-hook}. | |
894 | It does this by calling @code{run-mode-hooks}. If the major mode is a | |
895 | derived mode, that is if it calls another major mode (the parent mode) | |
896 | in its body, it should do this inside @code{delay-mode-hooks} so that | |
897 | the parent won't run these hooks itself. Instead, the derived mode's | |
898 | call to @code{run-mode-hooks} runs the parent's mode hook too. | |
899 | @xref{Major Mode Conventions}. | |
900 | ||
901 | Emacs versions before Emacs 22 did not have @code{delay-mode-hooks}. | |
902 | When user-implemented major modes have not been updated to use it, | |
903 | they won't entirely follow these conventions: they may run the | |
904 | parent's mode hook too early, or fail to run | |
905 | @code{after-change-major-mode-hook}. If you encounter such a major | |
906 | mode, please correct it to follow these conventions. | |
907 | ||
908 | When you defined a major mode using @code{define-derived-mode}, it | |
909 | automatically makes sure these conventions are followed. If you | |
910 | define a major mode ``by hand,'' not using @code{define-derived-mode}, | |
911 | use the following functions to handle these conventions automatically. | |
912 | ||
913 | @defun run-mode-hooks &rest hookvars | |
914 | Major modes should run their mode hook using this function. It is | |
915 | similar to @code{run-hooks} (@pxref{Hooks}), but it also runs | |
916 | @code{after-change-major-mode-hook}. | |
917 | ||
918 | When this function is called during the execution of a | |
919 | @code{delay-mode-hooks} form, it does not run the hooks immediately. | |
920 | Instead, it arranges for the next call to @code{run-mode-hooks} to run | |
921 | them. | |
922 | @end defun | |
923 | ||
924 | @defmac delay-mode-hooks body@dots{} | |
925 | When one major mode command calls another, it should do so inside of | |
926 | @code{delay-mode-hooks}. | |
927 | ||
928 | This macro executes @var{body}, but tells all @code{run-mode-hooks} | |
929 | calls during the execution of @var{body} to delay running their hooks. | |
930 | The hooks will actually run during the next call to | |
931 | @code{run-mode-hooks} after the end of the @code{delay-mode-hooks} | |
932 | construct. | |
933 | @end defmac | |
934 | ||
935 | @defvar after-change-major-mode-hook | |
936 | This is a normal hook run by @code{run-mode-hooks}. It is run at the | |
937 | very end of every properly-written major mode function. | |
938 | @end defvar | |
939 | ||
940 | @node Example Major Modes | |
941 | @subsection Major Mode Examples | |
942 | ||
943 | Text mode is perhaps the simplest mode besides Fundamental mode. | |
944 | Here are excerpts from @file{text-mode.el} that illustrate many of | |
945 | the conventions listed above: | |
946 | ||
947 | @smallexample | |
948 | @group | |
949 | ;; @r{Create the syntax table for this mode.} | |
950 | (defvar text-mode-syntax-table | |
951 | (let ((st (make-syntax-table))) | |
952 | (modify-syntax-entry ?\" ". " st) | |
953 | (modify-syntax-entry ?\\ ". " st) | |
954 | ;; Add `p' so M-c on `hello' leads to `Hello', not `hello'. | |
955 | (modify-syntax-entry ?' "w p" st) | |
956 | st) | |
957 | "Syntax table used while in `text-mode'.") | |
958 | @end group | |
959 | ||
960 | ;; @r{Create the keymap for this mode.} | |
961 | @group | |
962 | (defvar text-mode-map | |
963 | (let ((map (make-sparse-keymap))) | |
964 | (define-key map "\e\t" 'ispell-complete-word) | |
965 | (define-key map "\es" 'center-line) | |
966 | (define-key map "\eS" 'center-paragraph) | |
967 | map) | |
968 | "Keymap for `text-mode'. | |
969 | Many other modes, such as Mail mode, Outline mode | |
970 | and Indented Text mode, inherit all the commands | |
971 | defined in this map.") | |
972 | @end group | |
973 | @end smallexample | |
974 | ||
975 | Here is how the actual mode command is defined now: | |
976 | ||
977 | @smallexample | |
978 | @group | |
979 | (define-derived-mode text-mode nil "Text" | |
980 | "Major mode for editing text written for humans to read. | |
981 | In this mode, paragraphs are delimited only by blank or white lines. | |
982 | You can thus get the full benefit of adaptive filling | |
983 | (see the variable `adaptive-fill-mode'). | |
984 | \\@{text-mode-map@} | |
985 | Turning on Text mode runs the normal hook `text-mode-hook'." | |
986 | @end group | |
987 | @group | |
769741e3 | 988 | (set (make-local-variable 'text-mode-variant) t) |
b8d4c8d0 GM |
989 | ;; @r{These two lines are a feature added recently.} |
990 | (set (make-local-variable 'require-final-newline) | |
991 | mode-require-final-newline) | |
992 | (set (make-local-variable 'indent-line-function) 'indent-relative)) | |
993 | @end group | |
994 | @end smallexample | |
995 | ||
996 | @noindent | |
997 | (The last line is redundant nowadays, since @code{indent-relative} is | |
998 | the default value, and we'll delete it in a future version.) | |
999 | ||
1000 | Here is how it was defined formerly, before | |
1001 | @code{define-derived-mode} existed: | |
1002 | ||
1003 | @smallexample | |
1004 | @group | |
1005 | ;; @r{This isn't needed nowadays, since @code{define-derived-mode} does it.} | |
769741e3 | 1006 | (define-abbrev-table 'text-mode-abbrev-table () |
b8d4c8d0 | 1007 | "Abbrev table used while in text mode.") |
b8d4c8d0 GM |
1008 | @end group |
1009 | ||
1010 | @group | |
1011 | (defun text-mode () | |
1012 | "Major mode for editing text intended for humans to read... | |
1013 | Special commands: \\@{text-mode-map@} | |
1014 | @end group | |
1015 | @group | |
1016 | Turning on text-mode runs the hook `text-mode-hook'." | |
1017 | (interactive) | |
1018 | (kill-all-local-variables) | |
1019 | (use-local-map text-mode-map) | |
1020 | @end group | |
1021 | @group | |
1022 | (setq local-abbrev-table text-mode-abbrev-table) | |
1023 | (set-syntax-table text-mode-syntax-table) | |
1024 | @end group | |
1025 | @group | |
1026 | ;; @r{These four lines are absent from the current version} | |
1027 | ;; @r{not because this is done some other way, but rather} | |
1028 | ;; @r{because nowadays Text mode uses the normal definition of paragraphs.} | |
769741e3 SM |
1029 | (set (make-local-variable 'paragraph-start) |
1030 | (concat "[ \t]*$\\|" page-delimiter)) | |
1031 | (set (make-local-variable 'paragraph-separate) paragraph-start) | |
1032 | (set (make-local-variable 'indent-line-function) 'indent-relative-maybe) | |
b8d4c8d0 GM |
1033 | @end group |
1034 | @group | |
1035 | (setq mode-name "Text") | |
1036 | (setq major-mode 'text-mode) | |
1037 | (run-mode-hooks 'text-mode-hook)) ; @r{Finally, this permits the user to} | |
1038 | ; @r{customize the mode with a hook.} | |
1039 | @end group | |
1040 | @end smallexample | |
1041 | ||
1042 | @cindex @file{lisp-mode.el} | |
1043 | The three Lisp modes (Lisp mode, Emacs Lisp mode, and Lisp | |
1044 | Interaction mode) have more features than Text mode and the code is | |
1045 | correspondingly more complicated. Here are excerpts from | |
1046 | @file{lisp-mode.el} that illustrate how these modes are written. | |
1047 | ||
1048 | @cindex syntax table example | |
1049 | @smallexample | |
1050 | @group | |
1051 | ;; @r{Create mode-specific table variables.} | |
1052 | (defvar lisp-mode-syntax-table nil "") | |
1053 | (defvar lisp-mode-abbrev-table nil "") | |
1054 | @end group | |
1055 | ||
1056 | @group | |
1057 | (defvar emacs-lisp-mode-syntax-table | |
1058 | (let ((table (make-syntax-table))) | |
1059 | (let ((i 0)) | |
1060 | @end group | |
1061 | ||
1062 | @group | |
1063 | ;; @r{Set syntax of chars up to @samp{0} to say they are} | |
1064 | ;; @r{part of symbol names but not words.} | |
1065 | ;; @r{(The digit @samp{0} is @code{48} in the @acronym{ASCII} character set.)} | |
1066 | (while (< i ?0) | |
2f3725cd EZ |
1067 | (modify-syntax-entry i "_ " table) |
1068 | (setq i (1+ i))) | |
b8d4c8d0 GM |
1069 | ;; @r{@dots{} similar code follows for other character ranges.} |
1070 | @end group | |
1071 | @group | |
1072 | ;; @r{Then set the syntax codes for characters that are special in Lisp.} | |
1073 | (modify-syntax-entry ? " " table) | |
1074 | (modify-syntax-entry ?\t " " table) | |
1075 | (modify-syntax-entry ?\f " " table) | |
1076 | (modify-syntax-entry ?\n "> " table) | |
1077 | @end group | |
1078 | @group | |
1079 | ;; @r{Give CR the same syntax as newline, for selective-display.} | |
1080 | (modify-syntax-entry ?\^m "> " table) | |
1081 | (modify-syntax-entry ?\; "< " table) | |
1082 | (modify-syntax-entry ?` "' " table) | |
1083 | (modify-syntax-entry ?' "' " table) | |
1084 | (modify-syntax-entry ?, "' " table) | |
1085 | @end group | |
1086 | @group | |
1087 | ;; @r{@dots{}likewise for many other characters@dots{}} | |
1088 | (modify-syntax-entry ?\( "() " table) | |
1089 | (modify-syntax-entry ?\) ")( " table) | |
1090 | (modify-syntax-entry ?\[ "(] " table) | |
1091 | (modify-syntax-entry ?\] ")[ " table)) | |
1092 | table)) | |
1093 | @end group | |
1094 | @group | |
1095 | ;; @r{Create an abbrev table for lisp-mode.} | |
1096 | (define-abbrev-table 'lisp-mode-abbrev-table ()) | |
1097 | @end group | |
1098 | @end smallexample | |
1099 | ||
1100 | The three modes for Lisp share much of their code. For instance, | |
1101 | each calls the following function to set various variables: | |
1102 | ||
1103 | @smallexample | |
1104 | @group | |
1105 | (defun lisp-mode-variables (lisp-syntax) | |
1106 | (when lisp-syntax | |
1107 | (set-syntax-table lisp-mode-syntax-table)) | |
1108 | (setq local-abbrev-table lisp-mode-abbrev-table) | |
1109 | @dots{} | |
1110 | @end group | |
1111 | @end smallexample | |
1112 | ||
1113 | In Lisp and most programming languages, we want the paragraph | |
1114 | commands to treat only blank lines as paragraph separators. And the | |
1115 | modes should understand the Lisp conventions for comments. The rest of | |
1116 | @code{lisp-mode-variables} sets this up: | |
1117 | ||
1118 | @smallexample | |
1119 | @group | |
769741e3 SM |
1120 | (set (make-local-variable 'paragraph-start) (concat page-delimiter "\\|$" )) |
1121 | (set (make-local-variable 'paragraph-separate) paragraph-start) | |
b8d4c8d0 GM |
1122 | @dots{} |
1123 | @end group | |
1124 | @group | |
769741e3 | 1125 | (set (make-local-variable 'comment-indent-function) 'lisp-comment-indent)) |
b8d4c8d0 GM |
1126 | @dots{} |
1127 | @end group | |
1128 | @end smallexample | |
1129 | ||
1130 | Each of the different Lisp modes has a slightly different keymap. For | |
1131 | example, Lisp mode binds @kbd{C-c C-z} to @code{run-lisp}, but the other | |
1132 | Lisp modes do not. However, all Lisp modes have some commands in | |
1133 | common. The following code sets up the common commands: | |
1134 | ||
1135 | @smallexample | |
1136 | @group | |
769741e3 SM |
1137 | (defvar shared-lisp-mode-map |
1138 | (let ((map (make-sparse-keymap))) | |
1139 | (define-key shared-lisp-mode-map "\e\C-q" 'indent-sexp) | |
1140 | (define-key shared-lisp-mode-map "\177" | |
1141 | 'backward-delete-char-untabify) | |
1142 | map) | |
b8d4c8d0 | 1143 | "Keymap for commands shared by all sorts of Lisp modes.") |
b8d4c8d0 GM |
1144 | @end group |
1145 | @end smallexample | |
1146 | ||
1147 | @noindent | |
1148 | And here is the code to set up the keymap for Lisp mode: | |
1149 | ||
1150 | @smallexample | |
1151 | @group | |
769741e3 SM |
1152 | (defvar lisp-mode-map |
1153 | (let ((map (make-sparse-keymap))) | |
1154 | (set-keymap-parent map shared-lisp-mode-map) | |
1155 | (define-key map "\e\C-x" 'lisp-eval-defun) | |
1156 | (define-key map "\C-c\C-z" 'run-lisp) | |
1157 | map) | |
b8d4c8d0 | 1158 | "Keymap for ordinary Lisp mode...") |
b8d4c8d0 GM |
1159 | @end group |
1160 | @end smallexample | |
1161 | ||
1162 | Finally, here is the complete major mode function definition for | |
1163 | Lisp mode. | |
1164 | ||
1165 | @smallexample | |
1166 | @group | |
1167 | (defun lisp-mode () | |
1168 | "Major mode for editing Lisp code for Lisps other than GNU Emacs Lisp. | |
1169 | Commands: | |
1170 | Delete converts tabs to spaces as it moves back. | |
1171 | Blank lines separate paragraphs. Semicolons start comments. | |
1172 | \\@{lisp-mode-map@} | |
1173 | Note that `run-lisp' may be used either to start an inferior Lisp job | |
1174 | or to switch back to an existing one. | |
1175 | @end group | |
1176 | ||
1177 | @group | |
1178 | Entry to this mode calls the value of `lisp-mode-hook' | |
1179 | if that value is non-nil." | |
1180 | (interactive) | |
1181 | (kill-all-local-variables) | |
1182 | @end group | |
1183 | @group | |
1184 | (use-local-map lisp-mode-map) ; @r{Select the mode's keymap.} | |
1185 | (setq major-mode 'lisp-mode) ; @r{This is how @code{describe-mode}} | |
1186 | ; @r{finds out what to describe.} | |
1187 | (setq mode-name "Lisp") ; @r{This goes into the mode line.} | |
1188 | (lisp-mode-variables t) ; @r{This defines various variables.} | |
769741e3 SM |
1189 | (set (make-local-variable 'comment-start-skip) |
1190 | "\\(\\(^\\|[^\\\\\n]\\)\\(\\\\\\\\\\)*\\)\\(;+\\|#|\\) *") | |
1191 | (set (make-local-variable 'font-lock-keywords-case-fold-search) t) | |
b8d4c8d0 GM |
1192 | @end group |
1193 | @group | |
1194 | (setq imenu-case-fold-search t) | |
1195 | (set-syntax-table lisp-mode-syntax-table) | |
1196 | (run-mode-hooks 'lisp-mode-hook)) ; @r{This permits the user to use a} | |
1197 | ; @r{hook to customize the mode.} | |
1198 | @end group | |
1199 | @end smallexample | |
1200 | ||
1201 | @node Minor Modes | |
1202 | @section Minor Modes | |
1203 | @cindex minor mode | |
1204 | ||
1205 | A @dfn{minor mode} provides features that users may enable or disable | |
1206 | independently of the choice of major mode. Minor modes can be enabled | |
1207 | individually or in combination. Minor modes would be better named | |
1208 | ``generally available, optional feature modes,'' except that such a name | |
1209 | would be unwieldy. | |
1210 | ||
1211 | A minor mode is not usually meant as a variation of a single major mode. | |
1212 | Usually they are general and can apply to many major modes. For | |
1213 | example, Auto Fill mode works with any major mode that permits text | |
1214 | insertion. To be general, a minor mode must be effectively independent | |
1215 | of the things major modes do. | |
1216 | ||
1217 | A minor mode is often much more difficult to implement than a major | |
1218 | mode. One reason is that you should be able to activate and deactivate | |
1219 | minor modes in any order. A minor mode should be able to have its | |
1220 | desired effect regardless of the major mode and regardless of the other | |
1221 | minor modes in effect. | |
1222 | ||
1223 | Often the biggest problem in implementing a minor mode is finding a | |
1224 | way to insert the necessary hook into the rest of Emacs. Minor mode | |
1225 | keymaps make this easier than it used to be. | |
1226 | ||
1227 | @defvar minor-mode-list | |
1228 | The value of this variable is a list of all minor mode commands. | |
1229 | @end defvar | |
1230 | ||
1231 | @menu | |
1232 | * Minor Mode Conventions:: Tips for writing a minor mode. | |
1233 | * Keymaps and Minor Modes:: How a minor mode can have its own keymap. | |
1234 | * Defining Minor Modes:: A convenient facility for defining minor modes. | |
1235 | @end menu | |
1236 | ||
1237 | @node Minor Mode Conventions | |
1238 | @subsection Conventions for Writing Minor Modes | |
1239 | @cindex minor mode conventions | |
1240 | @cindex conventions for writing minor modes | |
1241 | ||
1242 | There are conventions for writing minor modes just as there are for | |
1243 | major modes. Several of the major mode conventions apply to minor | |
1244 | modes as well: those regarding the name of the mode initialization | |
1245 | function, the names of global symbols, the use of a hook at the end of | |
1246 | the initialization function, and the use of keymaps and other tables. | |
1247 | ||
1248 | In addition, there are several conventions that are specific to | |
1249 | minor modes. (The easiest way to follow all the conventions is to use | |
1250 | the macro @code{define-minor-mode}; @ref{Defining Minor Modes}.) | |
1251 | ||
1252 | @itemize @bullet | |
1253 | @item | |
1254 | @cindex mode variable | |
1255 | Make a variable whose name ends in @samp{-mode} to control the minor | |
1256 | mode. We call this the @dfn{mode variable}. The minor mode command | |
1257 | should set this variable (@code{nil} to disable; anything else to | |
1258 | enable). | |
1259 | ||
1260 | If possible, implement the mode so that setting the variable | |
1261 | automatically enables or disables the mode. Then the minor mode command | |
1262 | does not need to do anything except set the variable. | |
1263 | ||
1264 | This variable is used in conjunction with the @code{minor-mode-alist} to | |
1265 | display the minor mode name in the mode line. It can also enable | |
1266 | or disable a minor mode keymap. Individual commands or hooks can also | |
1267 | check the variable's value. | |
1268 | ||
1269 | If you want the minor mode to be enabled separately in each buffer, | |
1270 | make the variable buffer-local. | |
1271 | ||
1272 | @item | |
1273 | Define a command whose name is the same as the mode variable. | |
1274 | Its job is to enable and disable the mode by setting the variable. | |
1275 | ||
1276 | The command should accept one optional argument. If the argument is | |
1277 | @code{nil}, it should toggle the mode (turn it on if it is off, and | |
1278 | off if it is on). It should turn the mode on if the argument is a | |
1279 | positive integer, the symbol @code{t}, or a list whose @sc{car} is one | |
1280 | of those. It should turn the mode off if the argument is a negative | |
1281 | integer or zero, the symbol @code{-}, or a list whose @sc{car} is a | |
1282 | negative integer or zero. The meaning of other arguments is not | |
1283 | specified. | |
1284 | ||
1285 | Here is an example taken from the definition of @code{transient-mark-mode}. | |
1286 | It shows the use of @code{transient-mark-mode} as a variable that enables or | |
1287 | disables the mode's behavior, and also shows the proper way to toggle, | |
1288 | enable or disable the minor mode based on the raw prefix argument value. | |
1289 | ||
1290 | @smallexample | |
1291 | @group | |
1292 | (setq transient-mark-mode | |
1293 | (if (null arg) (not transient-mark-mode) | |
1294 | (> (prefix-numeric-value arg) 0))) | |
1295 | @end group | |
1296 | @end smallexample | |
1297 | ||
1298 | @item | |
1299 | Add an element to @code{minor-mode-alist} for each minor mode | |
1300 | (@pxref{Definition of minor-mode-alist}), if you want to indicate the | |
1301 | minor mode in the mode line. This element should be a list of the | |
1302 | following form: | |
1303 | ||
1304 | @smallexample | |
1305 | (@var{mode-variable} @var{string}) | |
1306 | @end smallexample | |
1307 | ||
1308 | Here @var{mode-variable} is the variable that controls enabling of the | |
1309 | minor mode, and @var{string} is a short string, starting with a space, | |
1310 | to represent the mode in the mode line. These strings must be short so | |
1311 | that there is room for several of them at once. | |
1312 | ||
1313 | When you add an element to @code{minor-mode-alist}, use @code{assq} to | |
1314 | check for an existing element, to avoid duplication. For example: | |
1315 | ||
1316 | @smallexample | |
1317 | @group | |
1318 | (unless (assq 'leif-mode minor-mode-alist) | |
1319 | (setq minor-mode-alist | |
1320 | (cons '(leif-mode " Leif") minor-mode-alist))) | |
1321 | @end group | |
1322 | @end smallexample | |
1323 | ||
1324 | @noindent | |
1325 | or like this, using @code{add-to-list} (@pxref{List Variables}): | |
1326 | ||
1327 | @smallexample | |
1328 | @group | |
1329 | (add-to-list 'minor-mode-alist '(leif-mode " Leif")) | |
1330 | @end group | |
1331 | @end smallexample | |
1332 | @end itemize | |
1333 | ||
1334 | Global minor modes distributed with Emacs should if possible support | |
1335 | enabling and disabling via Custom (@pxref{Customization}). To do this, | |
1336 | the first step is to define the mode variable with @code{defcustom}, and | |
0fc76035 | 1337 | specify @code{:type 'boolean}. |
b8d4c8d0 GM |
1338 | |
1339 | If just setting the variable is not sufficient to enable the mode, you | |
1340 | should also specify a @code{:set} method which enables the mode by | |
1341 | invoking the mode command. Note in the variable's documentation string that | |
1342 | setting the variable other than via Custom may not take effect. | |
1343 | ||
1344 | Also mark the definition with an autoload cookie (@pxref{autoload cookie}), | |
1345 | and specify a @code{:require} so that customizing the variable will load | |
1346 | the library that defines the mode. This will copy suitable definitions | |
1347 | into @file{loaddefs.el} so that users can use @code{customize-option} to | |
1348 | enable the mode. For example: | |
1349 | ||
1350 | @smallexample | |
1351 | @group | |
1352 | ||
1353 | ;;;###autoload | |
1354 | (defcustom msb-mode nil | |
1355 | "Toggle msb-mode. | |
1356 | Setting this variable directly does not take effect; | |
1357 | use either \\[customize] or the function `msb-mode'." | |
1358 | :set 'custom-set-minor-mode | |
1359 | :initialize 'custom-initialize-default | |
1360 | :version "20.4" | |
1361 | :type 'boolean | |
1362 | :group 'msb | |
1363 | :require 'msb) | |
1364 | @end group | |
1365 | @end smallexample | |
1366 | ||
1367 | @node Keymaps and Minor Modes | |
1368 | @subsection Keymaps and Minor Modes | |
1369 | ||
1370 | Each minor mode can have its own keymap, which is active when the mode | |
1371 | is enabled. To set up a keymap for a minor mode, add an element to the | |
1372 | alist @code{minor-mode-map-alist}. @xref{Definition of minor-mode-map-alist}. | |
1373 | ||
1374 | @cindex @code{self-insert-command}, minor modes | |
1375 | One use of minor mode keymaps is to modify the behavior of certain | |
1376 | self-inserting characters so that they do something else as well as | |
1377 | self-insert. In general, this is the only way to do that, since the | |
1378 | facilities for customizing @code{self-insert-command} are limited to | |
1379 | special cases (designed for abbrevs and Auto Fill mode). (Do not try | |
1380 | substituting your own definition of @code{self-insert-command} for the | |
1381 | standard one. The editor command loop handles this function specially.) | |
1382 | ||
1383 | The key sequences bound in a minor mode should consist of @kbd{C-c} | |
1384 | followed by one of @kbd{.,/?`'"[]\|~!#$%^&*()-_+=}. (The other | |
1385 | punctuation characters are reserved for major modes.) | |
1386 | ||
1387 | @node Defining Minor Modes | |
1388 | @subsection Defining Minor Modes | |
1389 | ||
1390 | The macro @code{define-minor-mode} offers a convenient way of | |
1391 | implementing a mode in one self-contained definition. | |
1392 | ||
1393 | @defmac define-minor-mode mode doc [init-value [lighter [keymap]]] keyword-args@dots{} body@dots{} | |
1394 | This macro defines a new minor mode whose name is @var{mode} (a | |
1395 | symbol). It defines a command named @var{mode} to toggle the minor | |
1396 | mode, with @var{doc} as its documentation string. It also defines a | |
1397 | variable named @var{mode}, which is set to @code{t} or @code{nil} by | |
1398 | enabling or disabling the mode. The variable is initialized to | |
1399 | @var{init-value}. Except in unusual circumstances (see below), this | |
1400 | value must be @code{nil}. | |
1401 | ||
1402 | The string @var{lighter} says what to display in the mode line | |
1403 | when the mode is enabled; if it is @code{nil}, the mode is not displayed | |
1404 | in the mode line. | |
1405 | ||
bc7d7ea6 CY |
1406 | The optional argument @var{keymap} specifies the keymap for the minor |
1407 | mode. If non-@code{nil}, it should be a variable name (whose value is | |
1408 | a keymap), a keymap, or an alist of the form | |
b8d4c8d0 GM |
1409 | |
1410 | @example | |
1411 | (@var{key-sequence} . @var{definition}) | |
1412 | @end example | |
1413 | ||
bc7d7ea6 CY |
1414 | @noindent |
1415 | where each @var{key-sequence} and @var{definition} are arguments | |
1416 | suitable for passing to @code{define-key} (@pxref{Changing Key | |
1417 | Bindings}). If @var{keymap} is a keymap or an alist, this also | |
1418 | defines the variable @code{@var{mode}-map}. | |
1419 | ||
b8d4c8d0 GM |
1420 | The above three arguments @var{init-value}, @var{lighter}, and |
1421 | @var{keymap} can be (partially) omitted when @var{keyword-args} are | |
1422 | used. The @var{keyword-args} consist of keywords followed by | |
1423 | corresponding values. A few keywords have special meanings: | |
1424 | ||
1425 | @table @code | |
1426 | @item :group @var{group} | |
1427 | Custom group name to use in all generated @code{defcustom} forms. | |
1428 | Defaults to @var{mode} without the possible trailing @samp{-mode}. | |
1429 | @strong{Warning:} don't use this default group name unless you have | |
1430 | written a @code{defgroup} to define that group properly. @xref{Group | |
1431 | Definitions}. | |
1432 | ||
1433 | @item :global @var{global} | |
1434 | If non-@code{nil}, this specifies that the minor mode should be global | |
1435 | rather than buffer-local. It defaults to @code{nil}. | |
1436 | ||
1437 | One of the effects of making a minor mode global is that the | |
1438 | @var{mode} variable becomes a customization variable. Toggling it | |
1439 | through the Custom interface turns the mode on and off, and its value | |
1440 | can be saved for future Emacs sessions (@pxref{Saving | |
1441 | Customizations,,, emacs, The GNU Emacs Manual}. For the saved | |
1442 | variable to work, you should ensure that the @code{define-minor-mode} | |
1443 | form is evaluated each time Emacs starts; for packages that are not | |
1444 | part of Emacs, the easiest way to do this is to specify a | |
1445 | @code{:require} keyword. | |
1446 | ||
1447 | @item :init-value @var{init-value} | |
1448 | This is equivalent to specifying @var{init-value} positionally. | |
1449 | ||
1450 | @item :lighter @var{lighter} | |
1451 | This is equivalent to specifying @var{lighter} positionally. | |
1452 | ||
1453 | @item :keymap @var{keymap} | |
1454 | This is equivalent to specifying @var{keymap} positionally. | |
1455 | @end table | |
1456 | ||
1457 | Any other keyword arguments are passed directly to the | |
1458 | @code{defcustom} generated for the variable @var{mode}. | |
1459 | ||
1460 | The command named @var{mode} first performs the standard actions such | |
1461 | as setting the variable named @var{mode} and then executes the | |
1462 | @var{body} forms, if any. It finishes by running the mode hook | |
1463 | variable @code{@var{mode}-hook}. | |
1464 | @end defmac | |
1465 | ||
1466 | The initial value must be @code{nil} except in cases where (1) the | |
1467 | mode is preloaded in Emacs, or (2) it is painless for loading to | |
1468 | enable the mode even though the user did not request it. For | |
1469 | instance, if the mode has no effect unless something else is enabled, | |
1470 | and will always be loaded by that time, enabling it by default is | |
1471 | harmless. But these are unusual circumstances. Normally, the | |
1472 | initial value must be @code{nil}. | |
1473 | ||
1474 | @findex easy-mmode-define-minor-mode | |
1475 | The name @code{easy-mmode-define-minor-mode} is an alias | |
1476 | for this macro. | |
1477 | ||
1478 | Here is an example of using @code{define-minor-mode}: | |
1479 | ||
1480 | @smallexample | |
1481 | (define-minor-mode hungry-mode | |
1482 | "Toggle Hungry mode. | |
1483 | With no argument, this command toggles the mode. | |
1484 | Non-null prefix argument turns on the mode. | |
1485 | Null prefix argument turns off the mode. | |
1486 | ||
1487 | When Hungry mode is enabled, the control delete key | |
1488 | gobbles all preceding whitespace except the last. | |
1489 | See the command \\[hungry-electric-delete]." | |
1490 | ;; The initial value. | |
1491 | nil | |
1492 | ;; The indicator for the mode line. | |
1493 | " Hungry" | |
1494 | ;; The minor mode bindings. | |
e8bf5266 | 1495 | '(([C-backspace] . hungry-electric-delete)) |
b8d4c8d0 GM |
1496 | :group 'hunger) |
1497 | @end smallexample | |
1498 | ||
1499 | @noindent | |
1500 | This defines a minor mode named ``Hungry mode,'' a command named | |
1501 | @code{hungry-mode} to toggle it, a variable named @code{hungry-mode} | |
1502 | which indicates whether the mode is enabled, and a variable named | |
1503 | @code{hungry-mode-map} which holds the keymap that is active when the | |
1504 | mode is enabled. It initializes the keymap with a key binding for | |
1505 | @kbd{C-@key{DEL}}. It puts the variable @code{hungry-mode} into | |
1506 | custom group @code{hunger}. There are no @var{body} forms---many | |
1507 | minor modes don't need any. | |
1508 | ||
1509 | Here's an equivalent way to write it: | |
1510 | ||
1511 | @smallexample | |
1512 | (define-minor-mode hungry-mode | |
1513 | "Toggle Hungry mode. | |
1514 | With no argument, this command toggles the mode. | |
1515 | Non-null prefix argument turns on the mode. | |
1516 | Null prefix argument turns off the mode. | |
1517 | ||
1518 | When Hungry mode is enabled, the control delete key | |
1519 | gobbles all preceding whitespace except the last. | |
1520 | See the command \\[hungry-electric-delete]." | |
1521 | ;; The initial value. | |
1522 | :init-value nil | |
1523 | ;; The indicator for the mode line. | |
1524 | :lighter " Hungry" | |
1525 | ;; The minor mode bindings. | |
1526 | :keymap | |
e8bf5266 JB |
1527 | '(([C-backspace] . hungry-electric-delete) |
1528 | ([C-M-backspace] | |
b8d4c8d0 GM |
1529 | . (lambda () |
1530 | (interactive) | |
1531 | (hungry-electric-delete t)))) | |
1532 | :group 'hunger) | |
1533 | @end smallexample | |
1534 | ||
1535 | @defmac define-globalized-minor-mode global-mode mode turn-on keyword-args@dots{} | |
1536 | This defines a global toggle named @var{global-mode} whose meaning is | |
1537 | to enable or disable the buffer-local minor mode @var{mode} in all | |
1538 | buffers. To turn on the minor mode in a buffer, it uses the function | |
1539 | @var{turn-on}; to turn off the minor mode, it calls @code{mode} with | |
1540 | @minus{}1 as argument. | |
1541 | ||
1542 | Globally enabling the mode also affects buffers subsequently created | |
1543 | by visiting files, and buffers that use a major mode other than | |
1544 | Fundamental mode; but it does not detect the creation of a new buffer | |
1545 | in Fundamental mode. | |
1546 | ||
1547 | This defines the customization option @var{global-mode} (@pxref{Customization}), | |
1548 | which can be toggled in the Custom interface to turn the minor mode on | |
1549 | and off. As with @code{define-minor-mode}, you should ensure that the | |
1550 | @code{define-globalized-minor-mode} form is evaluated each time Emacs | |
1551 | starts, for example by providing a @code{:require} keyword. | |
1552 | ||
1553 | Use @code{:group @var{group}} in @var{keyword-args} to specify the | |
1554 | custom group for the mode variable of the global minor mode. | |
1555 | @end defmac | |
1556 | ||
1557 | @node Mode Line Format | |
1558 | @section Mode-Line Format | |
1559 | @cindex mode line | |
1560 | ||
1561 | Each Emacs window (aside from minibuffer windows) typically has a mode | |
1562 | line at the bottom, which displays status information about the buffer | |
1563 | displayed in the window. The mode line contains information about the | |
1564 | buffer, such as its name, associated file, depth of recursive editing, | |
1565 | and major and minor modes. A window can also have a @dfn{header | |
1566 | line}, which is much like the mode line but appears at the top of the | |
1567 | window. | |
1568 | ||
1569 | This section describes how to control the contents of the mode line | |
1570 | and header line. We include it in this chapter because much of the | |
1571 | information displayed in the mode line relates to the enabled major and | |
1572 | minor modes. | |
1573 | ||
1574 | @menu | |
769741e3 SM |
1575 | * Base: Mode Line Basics. Basic ideas of mode line control. |
1576 | * Data: Mode Line Data. The data structure that controls the mode line. | |
1577 | * Top: Mode Line Top. The top level variable, mode-line-format. | |
1578 | * Mode Line Variables:: Variables used in that data structure. | |
1579 | * %-Constructs:: Putting information into a mode line. | |
1580 | * Properties in Mode:: Using text properties in the mode line. | |
1581 | * Header Lines:: Like a mode line, but at the top. | |
1582 | * Emulating Mode Line:: Formatting text as the mode line would. | |
b8d4c8d0 GM |
1583 | @end menu |
1584 | ||
1585 | @node Mode Line Basics | |
1586 | @subsection Mode Line Basics | |
1587 | ||
1588 | @code{mode-line-format} is a buffer-local variable that holds a | |
1589 | @dfn{mode line construct}, a kind of template, which controls what is | |
1590 | displayed on the mode line of the current buffer. The value of | |
1591 | @code{header-line-format} specifies the buffer's header line in the | |
1592 | same way. All windows for the same buffer use the same | |
1593 | @code{mode-line-format} and @code{header-line-format}. | |
1594 | ||
1595 | For efficiency, Emacs does not continuously recompute the mode | |
1596 | line and header line of a window. It does so when circumstances | |
1597 | appear to call for it---for instance, if you change the window | |
1598 | configuration, switch buffers, narrow or widen the buffer, scroll, or | |
1599 | change the buffer's modification status. If you modify any of the | |
1600 | variables referenced by @code{mode-line-format} (@pxref{Mode Line | |
1601 | Variables}), or any other variables and data structures that affect | |
1602 | how text is displayed (@pxref{Display}), you may want to force an | |
1603 | update of the mode line so as to display the new information or | |
1604 | display it in the new way. | |
1605 | ||
1606 | @defun force-mode-line-update &optional all | |
1607 | Force redisplay of the current buffer's mode line and header line. | |
1608 | The next redisplay will update the mode line and header line based on | |
1609 | the latest values of all relevant variables. With optional | |
1610 | non-@code{nil} @var{all}, force redisplay of all mode lines and header | |
1611 | lines. | |
1612 | ||
1613 | This function also forces recomputation of the menu bar menus | |
1614 | and the frame title. | |
1615 | @end defun | |
1616 | ||
1617 | The selected window's mode line is usually displayed in a different | |
1618 | color using the face @code{mode-line}. Other windows' mode lines | |
1619 | appear in the face @code{mode-line-inactive} instead. @xref{Faces}. | |
1620 | ||
1621 | @node Mode Line Data | |
1622 | @subsection The Data Structure of the Mode Line | |
1623 | @cindex mode-line construct | |
1624 | ||
1625 | The mode-line contents are controlled by a data structure called a | |
1626 | @dfn{mode-line construct}, made up of lists, strings, symbols, and | |
1627 | numbers kept in buffer-local variables. Each data type has a specific | |
1628 | meaning for the mode-line appearance, as described below. The same | |
1629 | data structure is used for constructing frame titles (@pxref{Frame | |
1630 | Titles}) and header lines (@pxref{Header Lines}). | |
1631 | ||
1632 | A mode-line construct may be as simple as a fixed string of text, | |
1633 | but it usually specifies how to combine fixed strings with variables' | |
1634 | values to construct the text. Many of these variables are themselves | |
1635 | defined to have mode-line constructs as their values. | |
1636 | ||
1637 | Here are the meanings of various data types as mode-line constructs: | |
1638 | ||
1639 | @table @code | |
1640 | @cindex percent symbol in mode line | |
1641 | @item @var{string} | |
1642 | A string as a mode-line construct appears verbatim except for | |
1643 | @dfn{@code{%}-constructs} in it. These stand for substitution of | |
1644 | other data; see @ref{%-Constructs}. | |
1645 | ||
1646 | If parts of the string have @code{face} properties, they control | |
1647 | display of the text just as they would text in the buffer. Any | |
1648 | characters which have no @code{face} properties are displayed, by | |
1649 | default, in the face @code{mode-line} or @code{mode-line-inactive} | |
1650 | (@pxref{Standard Faces,,, emacs, The GNU Emacs Manual}). The | |
1651 | @code{help-echo} and @code{local-map} properties in @var{string} have | |
1652 | special meanings. @xref{Properties in Mode}. | |
1653 | ||
1654 | @item @var{symbol} | |
1655 | A symbol as a mode-line construct stands for its value. The value of | |
1656 | @var{symbol} is used as a mode-line construct, in place of @var{symbol}. | |
1657 | However, the symbols @code{t} and @code{nil} are ignored, as is any | |
1658 | symbol whose value is void. | |
1659 | ||
1660 | There is one exception: if the value of @var{symbol} is a string, it is | |
1661 | displayed verbatim: the @code{%}-constructs are not recognized. | |
1662 | ||
1663 | Unless @var{symbol} is marked as ``risky'' (i.e., it has a | |
1664 | non-@code{nil} @code{risky-local-variable} property), all text | |
1665 | properties specified in @var{symbol}'s value are ignored. This | |
1666 | includes the text properties of strings in @var{symbol}'s value, as | |
1667 | well as all @code{:eval} and @code{:propertize} forms in it. (The | |
1668 | reason for this is security: non-risky variables could be set | |
1669 | automatically from file variables without prompting the user.) | |
1670 | ||
1671 | @item (@var{string} @var{rest}@dots{}) | |
1672 | @itemx (@var{list} @var{rest}@dots{}) | |
1673 | A list whose first element is a string or list means to process all the | |
1674 | elements recursively and concatenate the results. This is the most | |
1675 | common form of mode-line construct. | |
1676 | ||
1677 | @item (:eval @var{form}) | |
1678 | A list whose first element is the symbol @code{:eval} says to evaluate | |
1679 | @var{form}, and use the result as a string to display. Make sure this | |
1680 | evaluation cannot load any files, as doing so could cause infinite | |
1681 | recursion. | |
1682 | ||
1683 | @item (:propertize @var{elt} @var{props}@dots{}) | |
1684 | A list whose first element is the symbol @code{:propertize} says to | |
1685 | process the mode-line construct @var{elt} recursively, then add the text | |
1686 | properties specified by @var{props} to the result. The argument | |
1687 | @var{props} should consist of zero or more pairs @var{text-property} | |
1688 | @var{value}. (This feature is new as of Emacs 22.1.) | |
1689 | ||
1690 | @item (@var{symbol} @var{then} @var{else}) | |
1691 | A list whose first element is a symbol that is not a keyword specifies | |
1692 | a conditional. Its meaning depends on the value of @var{symbol}. If | |
1693 | @var{symbol} has a non-@code{nil} value, the second element, | |
1694 | @var{then}, is processed recursively as a mode-line element. | |
1695 | Otherwise, the third element, @var{else}, is processed recursively. | |
1696 | You may omit @var{else}; then the mode-line element displays nothing | |
1697 | if the value of @var{symbol} is @code{nil} or void. | |
1698 | ||
1699 | @item (@var{width} @var{rest}@dots{}) | |
1700 | A list whose first element is an integer specifies truncation or | |
1701 | padding of the results of @var{rest}. The remaining elements | |
1702 | @var{rest} are processed recursively as mode-line constructs and | |
1703 | concatenated together. When @var{width} is positive, the result is | |
1704 | space filled on the right if its width is less than @var{width}. When | |
1705 | @var{width} is negative, the result is truncated on the right to | |
1706 | @minus{}@var{width} columns if its width exceeds @minus{}@var{width}. | |
1707 | ||
1708 | For example, the usual way to show what percentage of a buffer is above | |
1709 | the top of the window is to use a list like this: @code{(-3 "%p")}. | |
1710 | @end table | |
1711 | ||
1712 | @node Mode Line Top | |
1713 | @subsection The Top Level of Mode Line Control | |
1714 | ||
1715 | The variable in overall control of the mode line is | |
1716 | @code{mode-line-format}. | |
1717 | ||
01f17ae2 | 1718 | @defopt mode-line-format |
b8d4c8d0 GM |
1719 | The value of this variable is a mode-line construct that controls the |
1720 | contents of the mode-line. It is always buffer-local in all buffers. | |
1721 | ||
1722 | If you set this variable to @code{nil} in a buffer, that buffer does | |
1723 | not have a mode line. (A window that is just one line tall never | |
1724 | displays a mode line.) | |
01f17ae2 | 1725 | @end defopt |
b8d4c8d0 GM |
1726 | |
1727 | The default value of @code{mode-line-format} is designed to use the | |
1728 | values of other variables such as @code{mode-line-position} and | |
1729 | @code{mode-line-modes} (which in turn incorporates the values of the | |
1730 | variables @code{mode-name} and @code{minor-mode-alist}). Very few | |
1731 | modes need to alter @code{mode-line-format} itself. For most | |
1732 | purposes, it is sufficient to alter some of the variables that | |
1733 | @code{mode-line-format} either directly or indirectly refers to. | |
1734 | ||
1735 | If you do alter @code{mode-line-format} itself, the new value should | |
1736 | use the same variables that appear in the default value (@pxref{Mode | |
1737 | Line Variables}), rather than duplicating their contents or displaying | |
1738 | the information in another fashion. This way, customizations made by | |
1739 | the user or by Lisp programs (such as @code{display-time} and major | |
1740 | modes) via changes to those variables remain effective. | |
1741 | ||
1742 | Here is an example of a @code{mode-line-format} that might be | |
1743 | useful for @code{shell-mode}, since it contains the host name and default | |
1744 | directory. | |
1745 | ||
1746 | @example | |
1747 | @group | |
1748 | (setq mode-line-format | |
1749 | (list "-" | |
1750 | 'mode-line-mule-info | |
1751 | 'mode-line-modified | |
1752 | 'mode-line-frame-identification | |
1753 | "%b--" | |
1754 | @end group | |
1755 | @group | |
1756 | ;; @r{Note that this is evaluated while making the list.} | |
1757 | ;; @r{It makes a mode-line construct which is just a string.} | |
1758 | (getenv "HOST") | |
1759 | @end group | |
1760 | ":" | |
1761 | 'default-directory | |
1762 | " " | |
1763 | 'global-mode-string | |
1764 | " %[(" | |
1765 | '(:eval (mode-line-mode-name)) | |
1766 | 'mode-line-process | |
1767 | 'minor-mode-alist | |
1768 | "%n" | |
1769 | ")%]--" | |
1770 | @group | |
1771 | '(which-func-mode ("" which-func-format "--")) | |
1772 | '(line-number-mode "L%l--") | |
1773 | '(column-number-mode "C%c--") | |
1774 | '(-3 "%p") | |
1775 | "-%-")) | |
1776 | @end group | |
1777 | @end example | |
1778 | ||
1779 | @noindent | |
1780 | (The variables @code{line-number-mode}, @code{column-number-mode} | |
1781 | and @code{which-func-mode} enable particular minor modes; as usual, | |
1782 | these variable names are also the minor mode command names.) | |
1783 | ||
1784 | @node Mode Line Variables | |
1785 | @subsection Variables Used in the Mode Line | |
1786 | ||
1787 | This section describes variables incorporated by the standard value | |
1788 | of @code{mode-line-format} into the text of the mode line. There is | |
1789 | nothing inherently special about these variables; any other variables | |
1790 | could have the same effects on the mode line if | |
1791 | @code{mode-line-format}'s value were changed to use them. However, | |
1792 | various parts of Emacs set these variables on the understanding that | |
1793 | they will control parts of the mode line; therefore, practically | |
1794 | speaking, it is essential for the mode line to use them. | |
1795 | ||
1796 | @defvar mode-line-mule-info | |
1797 | This variable holds the value of the mode-line construct that displays | |
1798 | information about the language environment, buffer coding system, and | |
1799 | current input method. @xref{Non-ASCII Characters}. | |
1800 | @end defvar | |
1801 | ||
1802 | @defvar mode-line-modified | |
1803 | This variable holds the value of the mode-line construct that displays | |
2079438a CY |
1804 | whether the current buffer is modified. Its default value displays |
1805 | @samp{**} if the buffer is modified, @samp{--} if the buffer is not | |
1806 | modified, @samp{%%} if the buffer is read only, and @samp{%*} if the | |
1807 | buffer is read only and modified. | |
b8d4c8d0 GM |
1808 | |
1809 | Changing this variable does not force an update of the mode line. | |
1810 | @end defvar | |
1811 | ||
1812 | @defvar mode-line-frame-identification | |
2079438a CY |
1813 | This variable identifies the current frame. Its default value |
1814 | displays @code{" "} if you are using a window system which can show | |
1815 | multiple frames, or @code{"-%F "} on an ordinary terminal which shows | |
1816 | only one frame at a time. | |
b8d4c8d0 GM |
1817 | @end defvar |
1818 | ||
1819 | @defvar mode-line-buffer-identification | |
2079438a CY |
1820 | This variable identifies the buffer being displayed in the window. |
1821 | Its default value displays the buffer name, padded with spaces to at | |
1822 | least 12 columns. | |
b8d4c8d0 GM |
1823 | @end defvar |
1824 | ||
01f17ae2 | 1825 | @defopt mode-line-position |
2079438a CY |
1826 | This variable indicates the position in the buffer. Its default value |
1827 | displays the buffer percentage and, optionally, the buffer size, the | |
1828 | line number and the column number. | |
01f17ae2 | 1829 | @end defopt |
b8d4c8d0 GM |
1830 | |
1831 | @defvar vc-mode | |
1832 | The variable @code{vc-mode}, buffer-local in each buffer, records | |
1833 | whether the buffer's visited file is maintained with version control, | |
1834 | and, if so, which kind. Its value is a string that appears in the mode | |
1835 | line, or @code{nil} for no version control. | |
1836 | @end defvar | |
1837 | ||
01f17ae2 | 1838 | @defopt mode-line-modes |
2079438a CY |
1839 | This variable displays the buffer's major and minor modes. Its |
1840 | default value also displays the recursive editing level, information | |
1841 | on the process status, and whether narrowing is in effect. | |
01f17ae2 | 1842 | @end defopt |
b8d4c8d0 GM |
1843 | |
1844 | The following three variables are used in @code{mode-line-modes}: | |
1845 | ||
1846 | @defvar mode-name | |
1847 | This buffer-local variable holds the ``pretty'' name of the current | |
9cf52b11 EZ |
1848 | buffer's major mode. Each major mode should set this variable so that |
1849 | the mode name will appear in the mode line. The value does not have | |
1850 | to be a string, but can use any of the data types valid in a mode-line | |
1851 | construct (@pxref{Mode Line Data}). To compute the string that will | |
1852 | identify the mode name in the mode line, use @code{format-mode-line} | |
1853 | (@pxref{Emulating Mode Line}). | |
b8d4c8d0 GM |
1854 | @end defvar |
1855 | ||
1856 | @defvar mode-line-process | |
1857 | This buffer-local variable contains the mode-line information on process | |
1858 | status in modes used for communicating with subprocesses. It is | |
1859 | displayed immediately following the major mode name, with no intervening | |
1860 | space. For example, its value in the @samp{*shell*} buffer is | |
1861 | @code{(":%s")}, which allows the shell to display its status along | |
1862 | with the major mode as: @samp{(Shell:run)}. Normally this variable | |
1863 | is @code{nil}. | |
1864 | @end defvar | |
1865 | ||
1866 | @defvar minor-mode-alist | |
1867 | @anchor{Definition of minor-mode-alist} | |
1868 | This variable holds an association list whose elements specify how the | |
1869 | mode line should indicate that a minor mode is active. Each element of | |
1870 | the @code{minor-mode-alist} should be a two-element list: | |
1871 | ||
1872 | @example | |
1873 | (@var{minor-mode-variable} @var{mode-line-string}) | |
1874 | @end example | |
1875 | ||
1876 | More generally, @var{mode-line-string} can be any mode-line spec. It | |
1877 | appears in the mode line when the value of @var{minor-mode-variable} | |
1878 | is non-@code{nil}, and not otherwise. These strings should begin with | |
1879 | spaces so that they don't run together. Conventionally, the | |
1880 | @var{minor-mode-variable} for a specific mode is set to a | |
1881 | non-@code{nil} value when that minor mode is activated. | |
1882 | ||
1883 | @code{minor-mode-alist} itself is not buffer-local. Each variable | |
1884 | mentioned in the alist should be buffer-local if its minor mode can be | |
1885 | enabled separately in each buffer. | |
1886 | @end defvar | |
1887 | ||
1888 | @defvar global-mode-string | |
1889 | This variable holds a mode-line spec that, by default, appears in the | |
1890 | mode line just after the @code{which-func-mode} minor mode if set, | |
1891 | else after @code{mode-line-modes}. The command @code{display-time} | |
1892 | sets @code{global-mode-string} to refer to the variable | |
1893 | @code{display-time-string}, which holds a string containing the time | |
1894 | and load information. | |
1895 | ||
1896 | The @samp{%M} construct substitutes the value of | |
1897 | @code{global-mode-string}, but that is obsolete, since the variable is | |
1898 | included in the mode line from @code{mode-line-format}. | |
1899 | @end defvar | |
1900 | ||
b8d4c8d0 | 1901 | Here is a simplified version of the default value of |
4e3b4528 | 1902 | @code{mode-line-format}. The real default value also |
b8d4c8d0 GM |
1903 | specifies addition of text properties. |
1904 | ||
1905 | @example | |
1906 | @group | |
1907 | ("-" | |
1908 | mode-line-mule-info | |
1909 | mode-line-modified | |
1910 | mode-line-frame-identification | |
1911 | mode-line-buffer-identification | |
1912 | @end group | |
1913 | " " | |
1914 | mode-line-position | |
1915 | (vc-mode vc-mode) | |
1916 | " " | |
1917 | @group | |
1918 | mode-line-modes | |
1919 | (which-func-mode ("" which-func-format "--")) | |
1920 | (global-mode-string ("--" global-mode-string)) | |
1921 | "-%-") | |
1922 | @end group | |
1923 | @end example | |
b8d4c8d0 GM |
1924 | |
1925 | @node %-Constructs | |
1926 | @subsection @code{%}-Constructs in the Mode Line | |
1927 | ||
1928 | Strings used as mode-line constructs can use certain | |
1929 | @code{%}-constructs to substitute various kinds of data. Here is a | |
1930 | list of the defined @code{%}-constructs, and what they mean. In any | |
1931 | construct except @samp{%%}, you can add a decimal integer after the | |
1932 | @samp{%} to specify a minimum field width. If the width is less, the | |
1933 | field is padded with spaces to the right. | |
1934 | ||
1935 | @table @code | |
1936 | @item %b | |
1937 | The current buffer name, obtained with the @code{buffer-name} function. | |
1938 | @xref{Buffer Names}. | |
1939 | ||
1940 | @item %c | |
1941 | The current column number of point. | |
1942 | ||
1943 | @item %e | |
1944 | When Emacs is nearly out of memory for Lisp objects, a brief message | |
1945 | saying so. Otherwise, this is empty. | |
1946 | ||
1947 | @item %f | |
1948 | The visited file name, obtained with the @code{buffer-file-name} | |
1949 | function. @xref{Buffer File Name}. | |
1950 | ||
1951 | @item %F | |
1952 | The title (only on a window system) or the name of the selected frame. | |
1953 | @xref{Basic Parameters}. | |
1954 | ||
1955 | @item %i | |
1956 | The size of the accessible part of the current buffer; basically | |
1957 | @code{(- (point-max) (point-min))}. | |
1958 | ||
1959 | @item %I | |
1960 | Like @samp{%i}, but the size is printed in a more readable way by using | |
1961 | @samp{k} for 10^3, @samp{M} for 10^6, @samp{G} for 10^9, etc., to | |
1962 | abbreviate. | |
1963 | ||
1964 | @item %l | |
1965 | The current line number of point, counting within the accessible portion | |
1966 | of the buffer. | |
1967 | ||
1968 | @item %n | |
1969 | @samp{Narrow} when narrowing is in effect; nothing otherwise (see | |
1970 | @code{narrow-to-region} in @ref{Narrowing}). | |
1971 | ||
1972 | @item %p | |
1973 | The percentage of the buffer text above the @strong{top} of window, or | |
1974 | @samp{Top}, @samp{Bottom} or @samp{All}. Note that the default | |
1975 | mode-line specification truncates this to three characters. | |
1976 | ||
1977 | @item %P | |
1978 | The percentage of the buffer text that is above the @strong{bottom} of | |
1979 | the window (which includes the text visible in the window, as well as | |
1980 | the text above the top), plus @samp{Top} if the top of the buffer is | |
1981 | visible on screen; or @samp{Bottom} or @samp{All}. | |
1982 | ||
1983 | @item %s | |
1984 | The status of the subprocess belonging to the current buffer, obtained with | |
1985 | @code{process-status}. @xref{Process Information}. | |
1986 | ||
1987 | @item %t | |
1988 | Whether the visited file is a text file or a binary file. This is a | |
1989 | meaningful distinction only on certain operating systems (@pxref{MS-DOS | |
1990 | File Types}). | |
1991 | ||
1992 | @item %z | |
1993 | The mnemonics of keyboard, terminal, and buffer coding systems. | |
1994 | ||
1995 | @item %Z | |
1996 | Like @samp{%z}, but including the end-of-line format. | |
1997 | ||
1998 | @item %* | |
1999 | @samp{%} if the buffer is read only (see @code{buffer-read-only}); @* | |
2000 | @samp{*} if the buffer is modified (see @code{buffer-modified-p}); @* | |
2001 | @samp{-} otherwise. @xref{Buffer Modification}. | |
2002 | ||
2003 | @item %+ | |
2004 | @samp{*} if the buffer is modified (see @code{buffer-modified-p}); @* | |
2005 | @samp{%} if the buffer is read only (see @code{buffer-read-only}); @* | |
2006 | @samp{-} otherwise. This differs from @samp{%*} only for a modified | |
2007 | read-only buffer. @xref{Buffer Modification}. | |
2008 | ||
2009 | @item %& | |
2010 | @samp{*} if the buffer is modified, and @samp{-} otherwise. | |
2011 | ||
2012 | @item %[ | |
2013 | An indication of the depth of recursive editing levels (not counting | |
2014 | minibuffer levels): one @samp{[} for each editing level. | |
2015 | @xref{Recursive Editing}. | |
2016 | ||
2017 | @item %] | |
2018 | One @samp{]} for each recursive editing level (not counting minibuffer | |
2019 | levels). | |
2020 | ||
2021 | @item %- | |
2022 | Dashes sufficient to fill the remainder of the mode line. | |
2023 | ||
2024 | @item %% | |
2025 | The character @samp{%}---this is how to include a literal @samp{%} in a | |
2026 | string in which @code{%}-constructs are allowed. | |
2027 | @end table | |
2028 | ||
2029 | The following two @code{%}-constructs are still supported, but they are | |
2030 | obsolete, since you can get the same results with the variables | |
2031 | @code{mode-name} and @code{global-mode-string}. | |
2032 | ||
2033 | @table @code | |
2034 | @item %m | |
2035 | The value of @code{mode-name}. | |
2036 | ||
2037 | @item %M | |
2038 | The value of @code{global-mode-string}. | |
2039 | @end table | |
2040 | ||
2041 | @node Properties in Mode | |
2042 | @subsection Properties in the Mode Line | |
2043 | @cindex text properties in the mode line | |
2044 | ||
2045 | Certain text properties are meaningful in the | |
2046 | mode line. The @code{face} property affects the appearance of text; the | |
2047 | @code{help-echo} property associates help strings with the text, and | |
2048 | @code{local-map} can make the text mouse-sensitive. | |
2049 | ||
2050 | There are four ways to specify text properties for text in the mode | |
2051 | line: | |
2052 | ||
2053 | @enumerate | |
2054 | @item | |
2055 | Put a string with a text property directly into the mode-line data | |
2056 | structure. | |
2057 | ||
2058 | @item | |
2059 | Put a text property on a mode-line %-construct such as @samp{%12b}; then | |
2060 | the expansion of the %-construct will have that same text property. | |
2061 | ||
2062 | @item | |
2063 | Use a @code{(:propertize @var{elt} @var{props}@dots{})} construct to | |
2064 | give @var{elt} a text property specified by @var{props}. | |
2065 | ||
2066 | @item | |
2067 | Use a list containing @code{:eval @var{form}} in the mode-line data | |
2068 | structure, and make @var{form} evaluate to a string that has a text | |
2069 | property. | |
2070 | @end enumerate | |
2071 | ||
2072 | You can use the @code{local-map} property to specify a keymap. This | |
2073 | keymap only takes real effect for mouse clicks; binding character keys | |
2074 | and function keys to it has no effect, since it is impossible to move | |
2075 | point into the mode line. | |
2076 | ||
2077 | When the mode line refers to a variable which does not have a | |
2078 | non-@code{nil} @code{risky-local-variable} property, any text | |
2079 | properties given or specified within that variable's values are | |
2080 | ignored. This is because such properties could otherwise specify | |
2081 | functions to be called, and those functions could come from file | |
2082 | local variables. | |
2083 | ||
2084 | @node Header Lines | |
2085 | @subsection Window Header Lines | |
2086 | @cindex header line (of a window) | |
2087 | @cindex window header line | |
2088 | ||
2089 | A window can have a @dfn{header line} at the | |
2090 | top, just as it can have a mode line at the bottom. The header line | |
2091 | feature works just like the mode-line feature, except that it's | |
2092 | controlled by different variables. | |
2093 | ||
2094 | @defvar header-line-format | |
2095 | This variable, local in every buffer, specifies how to display the | |
2096 | header line, for windows displaying the buffer. The format of the value | |
2097 | is the same as for @code{mode-line-format} (@pxref{Mode Line Data}). | |
b8d4c8d0 GM |
2098 | It is normally @code{nil}, so that ordinary buffers have no header line. |
2099 | @end defvar | |
2100 | ||
2101 | A window that is just one line tall never displays a header line. A | |
2102 | window that is two lines tall cannot display both a mode line and a | |
2103 | header line at once; if it has a mode line, then it does not display a | |
2104 | header line. | |
2105 | ||
2106 | @node Emulating Mode Line | |
2107 | @subsection Emulating Mode-Line Formatting | |
2108 | ||
2109 | You can use the function @code{format-mode-line} to compute | |
2110 | the text that would appear in a mode line or header line | |
2111 | based on a certain mode-line specification. | |
2112 | ||
2113 | @defun format-mode-line format &optional face window buffer | |
287e63bb EZ |
2114 | This function formats a line of text according to @var{format} as if it |
2115 | were generating the mode line for @var{window}, but it also returns the | |
2116 | text as a string. The argument @var{window} defaults to the selected | |
2117 | window. If @var{buffer} is non-@code{nil}, all the information used is | |
2118 | taken from @var{buffer}; by default, it comes from @var{window}'s | |
2119 | buffer. | |
b8d4c8d0 GM |
2120 | |
2121 | The value string normally has text properties that correspond to the | |
2e4ab211 EZ |
2122 | faces, keymaps, etc., that the mode line would have. Any character for |
2123 | which no @code{face} property is specified by @var{format} gets a | |
2124 | default value determined by @var{face}. If @var{face} is @code{t}, that | |
2125 | stands for either @code{mode-line} if @var{window} is selected, | |
2126 | otherwise @code{mode-line-inactive}. If @var{face} is @code{nil} or | |
2127 | omitted, that stands for the default face. If @var{face} is an integer, | |
2128 | the value returned by this function will have no text properties. | |
b8d4c8d0 | 2129 | |
287e63bb | 2130 | You can also specify other valid faces as the value of @var{face}. |
2e4ab211 EZ |
2131 | If specified, that face provides the @code{face} property for characters |
2132 | whose face is not specified by @var{format}. | |
287e63bb EZ |
2133 | |
2134 | Note that using @code{mode-line}, @code{mode-line-inactive}, or | |
2135 | @code{header-line} as @var{face} will actually redisplay the mode line | |
2136 | or the header line, respectively, using the current definitions of the | |
2137 | corresponding face, in addition to returning the formatted string. | |
2138 | (Other faces do not cause redisplay.) | |
2139 | ||
b8d4c8d0 GM |
2140 | For example, @code{(format-mode-line header-line-format)} returns the |
2141 | text that would appear in the selected window's header line (@code{""} | |
2142 | if it has no header line). @code{(format-mode-line header-line-format | |
2143 | 'header-line)} returns the same text, with each character | |
287e63bb EZ |
2144 | carrying the face that it will have in the header line itself, and also |
2145 | redraws the header line. | |
b8d4c8d0 GM |
2146 | @end defun |
2147 | ||
2148 | @node Imenu | |
2149 | @section Imenu | |
2150 | ||
2151 | @cindex Imenu | |
2152 | @dfn{Imenu} is a feature that lets users select a definition or | |
2153 | section in the buffer, from a menu which lists all of them, to go | |
2154 | directly to that location in the buffer. Imenu works by constructing | |
2155 | a buffer index which lists the names and buffer positions of the | |
2156 | definitions, or other named portions of the buffer; then the user can | |
2157 | choose one of them and move point to it. Major modes can add a menu | |
2158 | bar item to use Imenu using @code{imenu-add-to-menubar}. | |
2159 | ||
2160 | @defun imenu-add-to-menubar name | |
2161 | This function defines a local menu bar item named @var{name} | |
2162 | to run Imenu. | |
2163 | @end defun | |
2164 | ||
2165 | The user-level commands for using Imenu are described in the Emacs | |
2166 | Manual (@pxref{Imenu,, Imenu, emacs, the Emacs Manual}). This section | |
2167 | explains how to customize Imenu's method of finding definitions or | |
2168 | buffer portions for a particular major mode. | |
2169 | ||
2170 | The usual and simplest way is to set the variable | |
2171 | @code{imenu-generic-expression}: | |
2172 | ||
2173 | @defvar imenu-generic-expression | |
2174 | This variable, if non-@code{nil}, is a list that specifies regular | |
2175 | expressions for finding definitions for Imenu. Simple elements of | |
2176 | @code{imenu-generic-expression} look like this: | |
2177 | ||
2178 | @example | |
2179 | (@var{menu-title} @var{regexp} @var{index}) | |
2180 | @end example | |
2181 | ||
2182 | Here, if @var{menu-title} is non-@code{nil}, it says that the matches | |
2183 | for this element should go in a submenu of the buffer index; | |
2184 | @var{menu-title} itself specifies the name for the submenu. If | |
2185 | @var{menu-title} is @code{nil}, the matches for this element go directly | |
2186 | in the top level of the buffer index. | |
2187 | ||
2188 | The second item in the list, @var{regexp}, is a regular expression | |
2189 | (@pxref{Regular Expressions}); anything in the buffer that it matches | |
2190 | is considered a definition, something to mention in the buffer index. | |
2191 | The third item, @var{index}, is a non-negative integer that indicates | |
2192 | which subexpression in @var{regexp} matches the definition's name. | |
2193 | ||
2194 | An element can also look like this: | |
2195 | ||
2196 | @example | |
2197 | (@var{menu-title} @var{regexp} @var{index} @var{function} @var{arguments}@dots{}) | |
2198 | @end example | |
2199 | ||
2200 | Each match for this element creates an index item, and when the index | |
2201 | item is selected by the user, it calls @var{function} with arguments | |
2202 | consisting of the item name, the buffer position, and @var{arguments}. | |
2203 | ||
2204 | For Emacs Lisp mode, @code{imenu-generic-expression} could look like | |
2205 | this: | |
2206 | ||
2207 | @c should probably use imenu-syntax-alist and \\sw rather than [-A-Za-z0-9+] | |
2208 | @example | |
2209 | @group | |
2210 | ((nil "^\\s-*(def\\(un\\|subst\\|macro\\|advice\\)\ | |
2211 | \\s-+\\([-A-Za-z0-9+]+\\)" 2) | |
2212 | @end group | |
2213 | @group | |
2214 | ("*Vars*" "^\\s-*(def\\(var\\|const\\)\ | |
2215 | \\s-+\\([-A-Za-z0-9+]+\\)" 2) | |
2216 | @end group | |
2217 | @group | |
2218 | ("*Types*" | |
2219 | "^\\s-*\ | |
2220 | (def\\(type\\|struct\\|class\\|ine-condition\\)\ | |
2221 | \\s-+\\([-A-Za-z0-9+]+\\)" 2)) | |
2222 | @end group | |
2223 | @end example | |
2224 | ||
2225 | Setting this variable makes it buffer-local in the current buffer. | |
2226 | @end defvar | |
2227 | ||
2228 | @defvar imenu-case-fold-search | |
2229 | This variable controls whether matching against the regular | |
2230 | expressions in the value of @code{imenu-generic-expression} is | |
2231 | case-sensitive: @code{t}, the default, means matching should ignore | |
2232 | case. | |
2233 | ||
2234 | Setting this variable makes it buffer-local in the current buffer. | |
2235 | @end defvar | |
2236 | ||
2237 | @defvar imenu-syntax-alist | |
2238 | This variable is an alist of syntax table modifiers to use while | |
2239 | processing @code{imenu-generic-expression}, to override the syntax table | |
2240 | of the current buffer. Each element should have this form: | |
2241 | ||
2242 | @example | |
2243 | (@var{characters} . @var{syntax-description}) | |
2244 | @end example | |
2245 | ||
2246 | The @sc{car}, @var{characters}, can be either a character or a string. | |
2247 | The element says to give that character or characters the syntax | |
2248 | specified by @var{syntax-description}, which is passed to | |
2249 | @code{modify-syntax-entry} (@pxref{Syntax Table Functions}). | |
2250 | ||
2251 | This feature is typically used to give word syntax to characters which | |
2252 | normally have symbol syntax, and thus to simplify | |
2253 | @code{imenu-generic-expression} and speed up matching. | |
2254 | For example, Fortran mode uses it this way: | |
2255 | ||
2256 | @example | |
2257 | (setq imenu-syntax-alist '(("_$" . "w"))) | |
2258 | @end example | |
2259 | ||
2260 | The @code{imenu-generic-expression} regular expressions can then use | |
2261 | @samp{\\sw+} instead of @samp{\\(\\sw\\|\\s_\\)+}. Note that this | |
2262 | technique may be inconvenient when the mode needs to limit the initial | |
2263 | character of a name to a smaller set of characters than are allowed in | |
2264 | the rest of a name. | |
2265 | ||
2266 | Setting this variable makes it buffer-local in the current buffer. | |
2267 | @end defvar | |
2268 | ||
2269 | Another way to customize Imenu for a major mode is to set the | |
2270 | variables @code{imenu-prev-index-position-function} and | |
2271 | @code{imenu-extract-index-name-function}: | |
2272 | ||
2273 | @defvar imenu-prev-index-position-function | |
2274 | If this variable is non-@code{nil}, its value should be a function that | |
2275 | finds the next ``definition'' to put in the buffer index, scanning | |
2276 | backward in the buffer from point. It should return @code{nil} if it | |
2277 | doesn't find another ``definition'' before point. Otherwise it should | |
2278 | leave point at the place it finds a ``definition'' and return any | |
2279 | non-@code{nil} value. | |
2280 | ||
2281 | Setting this variable makes it buffer-local in the current buffer. | |
2282 | @end defvar | |
2283 | ||
2284 | @defvar imenu-extract-index-name-function | |
2285 | If this variable is non-@code{nil}, its value should be a function to | |
2286 | return the name for a definition, assuming point is in that definition | |
2287 | as the @code{imenu-prev-index-position-function} function would leave | |
2288 | it. | |
2289 | ||
2290 | Setting this variable makes it buffer-local in the current buffer. | |
2291 | @end defvar | |
2292 | ||
2293 | The last way to customize Imenu for a major mode is to set the | |
2294 | variable @code{imenu-create-index-function}: | |
2295 | ||
2296 | @defvar imenu-create-index-function | |
2297 | This variable specifies the function to use for creating a buffer | |
2298 | index. The function should take no arguments, and return an index | |
2299 | alist for the current buffer. It is called within | |
2300 | @code{save-excursion}, so where it leaves point makes no difference. | |
2301 | ||
2302 | The index alist can have three types of elements. Simple elements | |
2303 | look like this: | |
2304 | ||
2305 | @example | |
2306 | (@var{index-name} . @var{index-position}) | |
2307 | @end example | |
2308 | ||
2309 | Selecting a simple element has the effect of moving to position | |
2310 | @var{index-position} in the buffer. Special elements look like this: | |
2311 | ||
2312 | @example | |
2313 | (@var{index-name} @var{index-position} @var{function} @var{arguments}@dots{}) | |
2314 | @end example | |
2315 | ||
2316 | Selecting a special element performs: | |
2317 | ||
2318 | @example | |
2319 | (funcall @var{function} | |
2320 | @var{index-name} @var{index-position} @var{arguments}@dots{}) | |
2321 | @end example | |
2322 | ||
2323 | A nested sub-alist element looks like this: | |
2324 | ||
2325 | @example | |
2326 | (@var{menu-title} @var{sub-alist}) | |
2327 | @end example | |
2328 | ||
2329 | It creates the submenu @var{menu-title} specified by @var{sub-alist}. | |
2330 | ||
2331 | The default value of @code{imenu-create-index-function} is | |
2332 | @code{imenu-default-create-index-function}. This function calls the | |
2333 | value of @code{imenu-prev-index-position-function} and the value of | |
2334 | @code{imenu-extract-index-name-function} to produce the index alist. | |
2335 | However, if either of these two variables is @code{nil}, the default | |
2336 | function uses @code{imenu-generic-expression} instead. | |
2337 | ||
2338 | Setting this variable makes it buffer-local in the current buffer. | |
2339 | @end defvar | |
2340 | ||
2341 | @node Font Lock Mode | |
2342 | @section Font Lock Mode | |
2343 | @cindex Font Lock mode | |
2344 | ||
2345 | @dfn{Font Lock mode} is a feature that automatically attaches | |
2346 | @code{face} properties to certain parts of the buffer based on their | |
2347 | syntactic role. How it parses the buffer depends on the major mode; | |
2348 | most major modes define syntactic criteria for which faces to use in | |
2349 | which contexts. This section explains how to customize Font Lock for a | |
2350 | particular major mode. | |
2351 | ||
2352 | Font Lock mode finds text to highlight in two ways: through | |
2353 | syntactic parsing based on the syntax table, and through searching | |
2354 | (usually for regular expressions). Syntactic fontification happens | |
2355 | first; it finds comments and string constants and highlights them. | |
2356 | Search-based fontification happens second. | |
2357 | ||
2358 | @menu | |
2359 | * Font Lock Basics:: Overview of customizing Font Lock. | |
2360 | * Search-based Fontification:: Fontification based on regexps. | |
2361 | * Customizing Keywords:: Customizing search-based fontification. | |
2362 | * Other Font Lock Variables:: Additional customization facilities. | |
2363 | * Levels of Font Lock:: Each mode can define alternative levels | |
2364 | so that the user can select more or less. | |
769741e3 | 2365 | * Precalculated Fontification:: How Lisp programs that produce the buffer |
b8d4c8d0 GM |
2366 | contents can also specify how to fontify it. |
2367 | * Faces for Font Lock:: Special faces specifically for Font Lock. | |
2368 | * Syntactic Font Lock:: Fontification based on syntax tables. | |
2369 | * Setting Syntax Properties:: Defining character syntax based on context | |
2370 | using the Font Lock mechanism. | |
2371 | * Multiline Font Lock:: How to coerce Font Lock into properly | |
2372 | highlighting multiline constructs. | |
2373 | @end menu | |
2374 | ||
2375 | @node Font Lock Basics | |
2376 | @subsection Font Lock Basics | |
2377 | ||
2378 | There are several variables that control how Font Lock mode highlights | |
2379 | text. But major modes should not set any of these variables directly. | |
2380 | Instead, they should set @code{font-lock-defaults} as a buffer-local | |
2381 | variable. The value assigned to this variable is used, if and when Font | |
2382 | Lock mode is enabled, to set all the other variables. | |
2383 | ||
2384 | @defvar font-lock-defaults | |
2385 | This variable is set by major modes, as a buffer-local variable, to | |
2386 | specify how to fontify text in that mode. It automatically becomes | |
2387 | buffer-local when you set it. If its value is @code{nil}, Font-Lock | |
2388 | mode does no highlighting, and you can use the @samp{Faces} menu | |
2389 | (under @samp{Edit} and then @samp{Text Properties} in the menu bar) to | |
2390 | assign faces explicitly to text in the buffer. | |
2391 | ||
2392 | If non-@code{nil}, the value should look like this: | |
2393 | ||
2394 | @example | |
2395 | (@var{keywords} [@var{keywords-only} [@var{case-fold} | |
2396 | [@var{syntax-alist} [@var{syntax-begin} @var{other-vars}@dots{}]]]]) | |
2397 | @end example | |
2398 | ||
2399 | The first element, @var{keywords}, indirectly specifies the value of | |
2400 | @code{font-lock-keywords} which directs search-based fontification. | |
2401 | It can be a symbol, a variable or a function whose value is the list | |
2402 | to use for @code{font-lock-keywords}. It can also be a list of | |
2403 | several such symbols, one for each possible level of fontification. | |
caef3ed2 GM |
2404 | The first symbol specifies the @samp{mode default} level of |
2405 | fontification, the next symbol level 1 fontification, the next level 2, | |
2406 | and so on. The @samp{mode default} level is normally the same as level | |
2407 | 1. It is used when @code{font-lock-maximum-decoration} has a @code{nil} | |
2408 | value. @xref{Levels of Font Lock}. | |
b8d4c8d0 GM |
2409 | |
2410 | The second element, @var{keywords-only}, specifies the value of the | |
2411 | variable @code{font-lock-keywords-only}. If this is omitted or | |
2412 | @code{nil}, syntactic fontification (of strings and comments) is also | |
2413 | performed. If this is non-@code{nil}, such fontification is not | |
2414 | performed. @xref{Syntactic Font Lock}. | |
2415 | ||
2416 | The third element, @var{case-fold}, specifies the value of | |
2417 | @code{font-lock-keywords-case-fold-search}. If it is non-@code{nil}, | |
2418 | Font Lock mode ignores case when searching as directed by | |
2419 | @code{font-lock-keywords}. | |
2420 | ||
2421 | If the fourth element, @var{syntax-alist}, is non-@code{nil}, it | |
2422 | should be a list of cons cells of the form @code{(@var{char-or-string} | |
2423 | . @var{string})}. These are used to set up a syntax table for | |
2424 | syntactic fontification (@pxref{Syntax Table Functions}). The | |
2425 | resulting syntax table is stored in @code{font-lock-syntax-table}. | |
2426 | ||
2427 | The fifth element, @var{syntax-begin}, specifies the value of | |
2428 | @code{font-lock-beginning-of-syntax-function}. We recommend setting | |
2429 | this variable to @code{nil} and using @code{syntax-begin-function} | |
2430 | instead. | |
2431 | ||
2432 | All the remaining elements (if any) are collectively called | |
2433 | @var{other-vars}. Each of these elements should have the form | |
2434 | @code{(@var{variable} . @var{value})}---which means, make | |
2435 | @var{variable} buffer-local and then set it to @var{value}. You can | |
2436 | use these @var{other-vars} to set other variables that affect | |
2437 | fontification, aside from those you can control with the first five | |
2438 | elements. @xref{Other Font Lock Variables}. | |
2439 | @end defvar | |
2440 | ||
2441 | If your mode fontifies text explicitly by adding | |
2442 | @code{font-lock-face} properties, it can specify @code{(nil t)} for | |
2443 | @code{font-lock-defaults} to turn off all automatic fontification. | |
2444 | However, this is not required; it is possible to fontify some things | |
2445 | using @code{font-lock-face} properties and set up automatic | |
2446 | fontification for other parts of the text. | |
2447 | ||
2448 | @node Search-based Fontification | |
2449 | @subsection Search-based Fontification | |
2450 | ||
2451 | The most important variable for customizing Font Lock mode is | |
2452 | @code{font-lock-keywords}. It specifies the search criteria for | |
2453 | search-based fontification. You should specify the value of this | |
2454 | variable with @var{keywords} in @code{font-lock-defaults}. | |
2455 | ||
2456 | @defvar font-lock-keywords | |
2457 | This variable's value is a list of the keywords to highlight. Be | |
2458 | careful when composing regular expressions for this list; a poorly | |
2459 | written pattern can dramatically slow things down! | |
2460 | @end defvar | |
2461 | ||
2462 | Each element of @code{font-lock-keywords} specifies how to find | |
2463 | certain cases of text, and how to highlight those cases. Font Lock mode | |
2464 | processes the elements of @code{font-lock-keywords} one by one, and for | |
2465 | each element, it finds and handles all matches. Ordinarily, once | |
2466 | part of the text has been fontified already, this cannot be overridden | |
2467 | by a subsequent match in the same text; but you can specify different | |
2468 | behavior using the @var{override} element of a @var{subexp-highlighter}. | |
2469 | ||
2470 | Each element of @code{font-lock-keywords} should have one of these | |
2471 | forms: | |
2472 | ||
2473 | @table @code | |
2474 | @item @var{regexp} | |
2475 | Highlight all matches for @var{regexp} using | |
2476 | @code{font-lock-keyword-face}. For example, | |
2477 | ||
2478 | @example | |
2479 | ;; @r{Highlight occurrences of the word @samp{foo}} | |
2480 | ;; @r{using @code{font-lock-keyword-face}.} | |
2481 | "\\<foo\\>" | |
2482 | @end example | |
2483 | ||
2484 | The function @code{regexp-opt} (@pxref{Regexp Functions}) is useful | |
2485 | for calculating optimal regular expressions to match a number of | |
2486 | different keywords. | |
2487 | ||
2488 | @item @var{function} | |
2489 | Find text by calling @var{function}, and highlight the matches | |
2490 | it finds using @code{font-lock-keyword-face}. | |
2491 | ||
2492 | When @var{function} is called, it receives one argument, the limit of | |
2493 | the search; it should begin searching at point, and not search beyond the | |
2494 | limit. It should return non-@code{nil} if it succeeds, and set the | |
2495 | match data to describe the match that was found. Returning @code{nil} | |
2496 | indicates failure of the search. | |
2497 | ||
2498 | Fontification will call @var{function} repeatedly with the same limit, | |
2499 | and with point where the previous invocation left it, until | |
2500 | @var{function} fails. On failure, @var{function} need not reset point | |
2501 | in any particular way. | |
2502 | ||
2503 | @item (@var{matcher} . @var{subexp}) | |
2504 | In this kind of element, @var{matcher} is either a regular | |
2505 | expression or a function, as described above. The @sc{cdr}, | |
2506 | @var{subexp}, specifies which subexpression of @var{matcher} should be | |
2507 | highlighted (instead of the entire text that @var{matcher} matched). | |
2508 | ||
2509 | @example | |
2510 | ;; @r{Highlight the @samp{bar} in each occurrence of @samp{fubar},} | |
2511 | ;; @r{using @code{font-lock-keyword-face}.} | |
2512 | ("fu\\(bar\\)" . 1) | |
2513 | @end example | |
2514 | ||
2515 | If you use @code{regexp-opt} to produce the regular expression | |
2516 | @var{matcher}, you can use @code{regexp-opt-depth} (@pxref{Regexp | |
2517 | Functions}) to calculate the value for @var{subexp}. | |
2518 | ||
2519 | @item (@var{matcher} . @var{facespec}) | |
2520 | In this kind of element, @var{facespec} is an expression whose value | |
2521 | specifies the face to use for highlighting. In the simplest case, | |
2522 | @var{facespec} is a Lisp variable (a symbol) whose value is a face | |
2523 | name. | |
2524 | ||
2525 | @example | |
2526 | ;; @r{Highlight occurrences of @samp{fubar},} | |
2527 | ;; @r{using the face which is the value of @code{fubar-face}.} | |
2528 | ("fubar" . fubar-face) | |
2529 | @end example | |
2530 | ||
2531 | However, @var{facespec} can also evaluate to a list of this form: | |
2532 | ||
2533 | @example | |
2534 | (face @var{face} @var{prop1} @var{val1} @var{prop2} @var{val2}@dots{}) | |
2535 | @end example | |
2536 | ||
2537 | @noindent | |
2538 | to specify the face @var{face} and various additional text properties | |
2539 | to put on the text that matches. If you do this, be sure to add the | |
2540 | other text property names that you set in this way to the value of | |
2541 | @code{font-lock-extra-managed-props} so that the properties will also | |
2542 | be cleared out when they are no longer appropriate. Alternatively, | |
2543 | you can set the variable @code{font-lock-unfontify-region-function} to | |
2544 | a function that clears these properties. @xref{Other Font Lock | |
2545 | Variables}. | |
2546 | ||
2547 | @item (@var{matcher} . @var{subexp-highlighter}) | |
2548 | In this kind of element, @var{subexp-highlighter} is a list | |
2549 | which specifies how to highlight matches found by @var{matcher}. | |
2550 | It has the form: | |
2551 | ||
2552 | @example | |
e6c815ae | 2553 | (@var{subexp} @var{facespec} [@var{override} [@var{laxmatch}]]) |
b8d4c8d0 GM |
2554 | @end example |
2555 | ||
2556 | The @sc{car}, @var{subexp}, is an integer specifying which subexpression | |
2557 | of the match to fontify (0 means the entire matching text). The second | |
2558 | subelement, @var{facespec}, is an expression whose value specifies the | |
2559 | face, as described above. | |
2560 | ||
2561 | The last two values in @var{subexp-highlighter}, @var{override} and | |
2562 | @var{laxmatch}, are optional flags. If @var{override} is @code{t}, | |
2563 | this element can override existing fontification made by previous | |
2564 | elements of @code{font-lock-keywords}. If it is @code{keep}, then | |
2565 | each character is fontified if it has not been fontified already by | |
2566 | some other element. If it is @code{prepend}, the face specified by | |
2567 | @var{facespec} is added to the beginning of the @code{font-lock-face} | |
2568 | property. If it is @code{append}, the face is added to the end of the | |
2569 | @code{font-lock-face} property. | |
2570 | ||
2571 | If @var{laxmatch} is non-@code{nil}, it means there should be no error | |
2572 | if there is no subexpression numbered @var{subexp} in @var{matcher}. | |
2573 | Obviously, fontification of the subexpression numbered @var{subexp} will | |
2574 | not occur. However, fontification of other subexpressions (and other | |
2575 | regexps) will continue. If @var{laxmatch} is @code{nil}, and the | |
2576 | specified subexpression is missing, then an error is signaled which | |
2577 | terminates search-based fontification. | |
2578 | ||
2579 | Here are some examples of elements of this kind, and what they do: | |
2580 | ||
2581 | @smallexample | |
2582 | ;; @r{Highlight occurrences of either @samp{foo} or @samp{bar}, using} | |
2583 | ;; @r{@code{foo-bar-face}, even if they have already been highlighted.} | |
2584 | ;; @r{@code{foo-bar-face} should be a variable whose value is a face.} | |
2585 | ("foo\\|bar" 0 foo-bar-face t) | |
2586 | ||
2587 | ;; @r{Highlight the first subexpression within each occurrence} | |
2588 | ;; @r{that the function @code{fubar-match} finds,} | |
2589 | ;; @r{using the face which is the value of @code{fubar-face}.} | |
2590 | (fubar-match 1 fubar-face) | |
2591 | @end smallexample | |
2592 | ||
2593 | @item (@var{matcher} . @var{anchored-highlighter}) | |
2594 | In this kind of element, @var{anchored-highlighter} specifies how to | |
2595 | highlight text that follows a match found by @var{matcher}. So a | |
2596 | match found by @var{matcher} acts as the anchor for further searches | |
2597 | specified by @var{anchored-highlighter}. @var{anchored-highlighter} | |
2598 | is a list of the following form: | |
2599 | ||
2600 | @example | |
2601 | (@var{anchored-matcher} @var{pre-form} @var{post-form} | |
2602 | @var{subexp-highlighters}@dots{}) | |
2603 | @end example | |
2604 | ||
2605 | Here, @var{anchored-matcher}, like @var{matcher}, is either a regular | |
2606 | expression or a function. After a match of @var{matcher} is found, | |
2607 | point is at the end of the match. Now, Font Lock evaluates the form | |
2608 | @var{pre-form}. Then it searches for matches of | |
2609 | @var{anchored-matcher} and uses @var{subexp-highlighters} to highlight | |
2610 | these. A @var{subexp-highlighter} is as described above. Finally, | |
2611 | Font Lock evaluates @var{post-form}. | |
2612 | ||
2613 | The forms @var{pre-form} and @var{post-form} can be used to initialize | |
2614 | before, and cleanup after, @var{anchored-matcher} is used. Typically, | |
2615 | @var{pre-form} is used to move point to some position relative to the | |
2616 | match of @var{matcher}, before starting with @var{anchored-matcher}. | |
2617 | @var{post-form} might be used to move back, before resuming with | |
2618 | @var{matcher}. | |
2619 | ||
2620 | After Font Lock evaluates @var{pre-form}, it does not search for | |
2621 | @var{anchored-matcher} beyond the end of the line. However, if | |
2622 | @var{pre-form} returns a buffer position that is greater than the | |
2623 | position of point after @var{pre-form} is evaluated, then the position | |
2624 | returned by @var{pre-form} is used as the limit of the search instead. | |
2625 | It is generally a bad idea to return a position greater than the end | |
2626 | of the line; in other words, the @var{anchored-matcher} search should | |
2627 | not span lines. | |
2628 | ||
2629 | For example, | |
2630 | ||
2631 | @smallexample | |
2632 | ;; @r{Highlight occurrences of the word @samp{item} following} | |
2633 | ;; @r{an occurrence of the word @samp{anchor} (on the same line)} | |
2634 | ;; @r{in the value of @code{item-face}.} | |
2635 | ("\\<anchor\\>" "\\<item\\>" nil nil (0 item-face)) | |
2636 | @end smallexample | |
2637 | ||
2638 | Here, @var{pre-form} and @var{post-form} are @code{nil}. Therefore | |
2639 | searching for @samp{item} starts at the end of the match of | |
2640 | @samp{anchor}, and searching for subsequent instances of @samp{anchor} | |
2641 | resumes from where searching for @samp{item} concluded. | |
2642 | ||
2643 | @item (@var{matcher} @var{highlighters}@dots{}) | |
2644 | This sort of element specifies several @var{highlighter} lists for a | |
2645 | single @var{matcher}. A @var{highlighter} list can be of the type | |
2646 | @var{subexp-highlighter} or @var{anchored-highlighter} as described | |
2647 | above. | |
2648 | ||
2649 | For example, | |
2650 | ||
2651 | @smallexample | |
2652 | ;; @r{Highlight occurrences of the word @samp{anchor} in the value} | |
2653 | ;; @r{of @code{anchor-face}, and subsequent occurrences of the word} | |
2654 | ;; @r{@samp{item} (on the same line) in the value of @code{item-face}.} | |
2655 | ("\\<anchor\\>" (0 anchor-face) | |
2656 | ("\\<item\\>" nil nil (0 item-face))) | |
2657 | @end smallexample | |
2658 | ||
2659 | @item (eval . @var{form}) | |
2660 | Here @var{form} is an expression to be evaluated the first time | |
2661 | this value of @code{font-lock-keywords} is used in a buffer. | |
2662 | Its value should have one of the forms described in this table. | |
2663 | @end table | |
2664 | ||
2665 | @strong{Warning:} Do not design an element of @code{font-lock-keywords} | |
2666 | to match text which spans lines; this does not work reliably. | |
2667 | For details, see @xref{Multiline Font Lock}. | |
2668 | ||
2669 | You can use @var{case-fold} in @code{font-lock-defaults} to specify | |
2670 | the value of @code{font-lock-keywords-case-fold-search} which says | |
2671 | whether search-based fontification should be case-insensitive. | |
2672 | ||
2673 | @defvar font-lock-keywords-case-fold-search | |
2674 | Non-@code{nil} means that regular expression matching for the sake of | |
2675 | @code{font-lock-keywords} should be case-insensitive. | |
2676 | @end defvar | |
2677 | ||
2678 | @node Customizing Keywords | |
2679 | @subsection Customizing Search-Based Fontification | |
2680 | ||
2681 | You can use @code{font-lock-add-keywords} to add additional | |
2682 | search-based fontification rules to a major mode, and | |
867d4bb3 | 2683 | @code{font-lock-remove-keywords} to remove rules. |
b8d4c8d0 GM |
2684 | |
2685 | @defun font-lock-add-keywords mode keywords &optional how | |
2686 | This function adds highlighting @var{keywords}, for the current buffer | |
2687 | or for major mode @var{mode}. The argument @var{keywords} should be a | |
2688 | list with the same format as the variable @code{font-lock-keywords}. | |
2689 | ||
2690 | If @var{mode} is a symbol which is a major mode command name, such as | |
2691 | @code{c-mode}, the effect is that enabling Font Lock mode in | |
2692 | @var{mode} will add @var{keywords} to @code{font-lock-keywords}. | |
2693 | Calling with a non-@code{nil} value of @var{mode} is correct only in | |
2694 | your @file{~/.emacs} file. | |
2695 | ||
2696 | If @var{mode} is @code{nil}, this function adds @var{keywords} to | |
2697 | @code{font-lock-keywords} in the current buffer. This way of calling | |
2698 | @code{font-lock-add-keywords} is usually used in mode hook functions. | |
2699 | ||
2700 | By default, @var{keywords} are added at the beginning of | |
2701 | @code{font-lock-keywords}. If the optional argument @var{how} is | |
2702 | @code{set}, they are used to replace the value of | |
2703 | @code{font-lock-keywords}. If @var{how} is any other non-@code{nil} | |
2704 | value, they are added at the end of @code{font-lock-keywords}. | |
2705 | ||
2706 | Some modes provide specialized support you can use in additional | |
2707 | highlighting patterns. See the variables | |
2708 | @code{c-font-lock-extra-types}, @code{c++-font-lock-extra-types}, | |
2709 | and @code{java-font-lock-extra-types}, for example. | |
2710 | ||
2711 | @strong{Warning:} major mode functions must not call | |
2712 | @code{font-lock-add-keywords} under any circumstances, either directly | |
2713 | or indirectly, except through their mode hooks. (Doing so would lead | |
2714 | to incorrect behavior for some minor modes.) They should set up their | |
2715 | rules for search-based fontification by setting | |
2716 | @code{font-lock-keywords}. | |
2717 | @end defun | |
2718 | ||
2719 | @defun font-lock-remove-keywords mode keywords | |
2720 | This function removes @var{keywords} from @code{font-lock-keywords} | |
2721 | for the current buffer or for major mode @var{mode}. As in | |
2722 | @code{font-lock-add-keywords}, @var{mode} should be a major mode | |
2723 | command name or @code{nil}. All the caveats and requirements for | |
2724 | @code{font-lock-add-keywords} apply here too. | |
2725 | @end defun | |
2726 | ||
2727 | For example, this code | |
2728 | ||
2729 | @smallexample | |
2730 | (font-lock-add-keywords 'c-mode | |
2731 | '(("\\<\\(FIXME\\):" 1 font-lock-warning-face prepend) | |
2732 | ("\\<\\(and\\|or\\|not\\)\\>" . font-lock-keyword-face))) | |
2733 | @end smallexample | |
2734 | ||
2735 | @noindent | |
2736 | adds two fontification patterns for C mode: one to fontify the word | |
2737 | @samp{FIXME}, even in comments, and another to fontify the words | |
2738 | @samp{and}, @samp{or} and @samp{not} as keywords. | |
2739 | ||
2740 | @noindent | |
2741 | That example affects only C mode proper. To add the same patterns to | |
2742 | C mode @emph{and} all modes derived from it, do this instead: | |
2743 | ||
2744 | @smallexample | |
2745 | (add-hook 'c-mode-hook | |
2746 | (lambda () | |
2747 | (font-lock-add-keywords nil | |
2748 | '(("\\<\\(FIXME\\):" 1 font-lock-warning-face prepend) | |
2749 | ("\\<\\(and\\|or\\|not\\)\\>" . | |
2750 | font-lock-keyword-face))))) | |
2751 | @end smallexample | |
2752 | ||
2753 | @node Other Font Lock Variables | |
2754 | @subsection Other Font Lock Variables | |
2755 | ||
2756 | This section describes additional variables that a major mode can | |
2757 | set by means of @var{other-vars} in @code{font-lock-defaults} | |
2758 | (@pxref{Font Lock Basics}). | |
2759 | ||
2760 | @defvar font-lock-mark-block-function | |
2761 | If this variable is non-@code{nil}, it should be a function that is | |
2762 | called with no arguments, to choose an enclosing range of text for | |
2763 | refontification for the command @kbd{M-o M-o} | |
2764 | (@code{font-lock-fontify-block}). | |
2765 | ||
2766 | The function should report its choice by placing the region around it. | |
2767 | A good choice is a range of text large enough to give proper results, | |
2768 | but not too large so that refontification becomes slow. Typical values | |
2769 | are @code{mark-defun} for programming modes or @code{mark-paragraph} for | |
2770 | textual modes. | |
2771 | @end defvar | |
2772 | ||
2773 | @defvar font-lock-extra-managed-props | |
2774 | This variable specifies additional properties (other than | |
2775 | @code{font-lock-face}) that are being managed by Font Lock mode. It | |
2776 | is used by @code{font-lock-default-unfontify-region}, which normally | |
2777 | only manages the @code{font-lock-face} property. If you want Font | |
2778 | Lock to manage other properties as well, you must specify them in a | |
2779 | @var{facespec} in @code{font-lock-keywords} as well as add them to | |
2780 | this list. @xref{Search-based Fontification}. | |
2781 | @end defvar | |
2782 | ||
2783 | @defvar font-lock-fontify-buffer-function | |
2784 | Function to use for fontifying the buffer. The default value is | |
2785 | @code{font-lock-default-fontify-buffer}. | |
2786 | @end defvar | |
2787 | ||
2788 | @defvar font-lock-unfontify-buffer-function | |
2789 | Function to use for unfontifying the buffer. This is used when | |
2790 | turning off Font Lock mode. The default value is | |
2791 | @code{font-lock-default-unfontify-buffer}. | |
2792 | @end defvar | |
2793 | ||
2794 | @defvar font-lock-fontify-region-function | |
2795 | Function to use for fontifying a region. It should take two | |
2796 | arguments, the beginning and end of the region, and an optional third | |
2797 | argument @var{verbose}. If @var{verbose} is non-@code{nil}, the | |
2798 | function should print status messages. The default value is | |
2799 | @code{font-lock-default-fontify-region}. | |
2800 | @end defvar | |
2801 | ||
2802 | @defvar font-lock-unfontify-region-function | |
2803 | Function to use for unfontifying a region. It should take two | |
2804 | arguments, the beginning and end of the region. The default value is | |
2805 | @code{font-lock-default-unfontify-region}. | |
2806 | @end defvar | |
2807 | ||
e070558d CY |
2808 | @defun jit-lock-register function &optional contextual |
2809 | This function tells Font Lock mode to run the Lisp function | |
2810 | @var{function} any time it has to fontify or refontify part of the | |
2811 | current buffer. It calls @var{function} before calling the default | |
2812 | fontification functions, and gives it two arguments, @var{start} and | |
2813 | @var{end}, which specify the region to be fontified or refontified. | |
2814 | ||
2815 | The optional argument @var{contextual}, if non-@code{nil}, forces Font | |
2816 | Lock mode to always refontify a syntactically relevant part of the | |
2817 | buffer, and not just the modified lines. This argument can usually be | |
2818 | omitted. | |
2819 | @end defun | |
2820 | ||
2821 | @defun jit-lock-unregister function | |
2822 | If @var{function} was previously registered as a fontification | |
2823 | function using @code{jit-lock-register}, this function unregisters it. | |
2824 | @end defun | |
b8d4c8d0 GM |
2825 | |
2826 | @node Levels of Font Lock | |
2827 | @subsection Levels of Font Lock | |
2828 | ||
2829 | Many major modes offer three different levels of fontification. You | |
2830 | can define multiple levels by using a list of symbols for @var{keywords} | |
2831 | in @code{font-lock-defaults}. Each symbol specifies one level of | |
caef3ed2 GM |
2832 | fontification; it is up to the user to choose one of these levels, |
2833 | normally by setting @code{font-lock-maximum-decoration} (@pxref{Font | |
2834 | Lock,,, emacs, the GNU Emacs Manual}). The chosen level's symbol | |
2835 | value is used to initialize @code{font-lock-keywords}. | |
b8d4c8d0 GM |
2836 | |
2837 | Here are the conventions for how to define the levels of | |
2838 | fontification: | |
2839 | ||
2840 | @itemize @bullet | |
2841 | @item | |
2842 | Level 1: highlight function declarations, file directives (such as include or | |
2843 | import directives), strings and comments. The idea is speed, so only | |
2844 | the most important and top-level components are fontified. | |
2845 | ||
2846 | @item | |
2847 | Level 2: in addition to level 1, highlight all language keywords, | |
2848 | including type names that act like keywords, as well as named constant | |
2849 | values. The idea is that all keywords (either syntactic or semantic) | |
2850 | should be fontified appropriately. | |
2851 | ||
2852 | @item | |
2853 | Level 3: in addition to level 2, highlight the symbols being defined in | |
2854 | function and variable declarations, and all builtin function names, | |
2855 | wherever they appear. | |
2856 | @end itemize | |
2857 | ||
2858 | @node Precalculated Fontification | |
2859 | @subsection Precalculated Fontification | |
2860 | ||
eae7d8f8 RS |
2861 | Some major modes such as @code{list-buffers} and @code{occur} |
2862 | construct the buffer text programmatically. The easiest way for them | |
2863 | to support Font Lock mode is to specify the faces of text when they | |
2864 | insert the text in the buffer. | |
2865 | ||
2866 | The way to do this is to specify the faces in the text with the | |
2867 | special text property @code{font-lock-face} (@pxref{Special | |
2868 | Properties}). When Font Lock mode is enabled, this property controls | |
2869 | the display, just like the @code{face} property. When Font Lock mode | |
2870 | is disabled, @code{font-lock-face} has no effect on the display. | |
2871 | ||
2872 | It is ok for a mode to use @code{font-lock-face} for some text and | |
2873 | also use the normal Font Lock machinery. But if the mode does not use | |
2874 | the normal Font Lock machinery, it should not set the variable | |
2875 | @code{font-lock-defaults}. | |
b8d4c8d0 GM |
2876 | |
2877 | @node Faces for Font Lock | |
2878 | @subsection Faces for Font Lock | |
2879 | @cindex faces for font lock | |
2880 | @cindex font lock faces | |
2881 | ||
2882 | You can make Font Lock mode use any face, but several faces are | |
2883 | defined specifically for Font Lock mode. Each of these symbols is both | |
2884 | a face name, and a variable whose default value is the symbol itself. | |
2885 | Thus, the default value of @code{font-lock-comment-face} is | |
2886 | @code{font-lock-comment-face}. This means you can write | |
2887 | @code{font-lock-comment-face} in a context such as | |
2888 | @code{font-lock-keywords} where a face-name-valued expression is used. | |
2889 | ||
2890 | @table @code | |
2891 | @item font-lock-comment-face | |
2892 | @vindex font-lock-comment-face | |
2893 | Used (typically) for comments. | |
2894 | ||
2895 | @item font-lock-comment-delimiter-face | |
2896 | @vindex font-lock-comment-delimiter-face | |
2897 | Used (typically) for comments delimiters. | |
2898 | ||
2899 | @item font-lock-doc-face | |
2900 | @vindex font-lock-doc-face | |
2901 | Used (typically) for documentation strings in the code. | |
2902 | ||
2903 | @item font-lock-string-face | |
2904 | @vindex font-lock-string-face | |
2905 | Used (typically) for string constants. | |
2906 | ||
2907 | @item font-lock-keyword-face | |
2908 | @vindex font-lock-keyword-face | |
2909 | Used (typically) for keywords---names that have special syntactic | |
2910 | significance, like @code{for} and @code{if} in C. | |
2911 | ||
2912 | @item font-lock-builtin-face | |
2913 | @vindex font-lock-builtin-face | |
2914 | Used (typically) for built-in function names. | |
2915 | ||
2916 | @item font-lock-function-name-face | |
2917 | @vindex font-lock-function-name-face | |
2918 | Used (typically) for the name of a function being defined or declared, | |
2919 | in a function definition or declaration. | |
2920 | ||
2921 | @item font-lock-variable-name-face | |
2922 | @vindex font-lock-variable-name-face | |
2923 | Used (typically) for the name of a variable being defined or declared, | |
2924 | in a variable definition or declaration. | |
2925 | ||
2926 | @item font-lock-type-face | |
2927 | @vindex font-lock-type-face | |
2928 | Used (typically) for names of user-defined data types, | |
2929 | where they are defined and where they are used. | |
2930 | ||
2931 | @item font-lock-constant-face | |
2932 | @vindex font-lock-constant-face | |
2933 | Used (typically) for constant names. | |
2934 | ||
2935 | @item font-lock-preprocessor-face | |
2936 | @vindex font-lock-preprocessor-face | |
2937 | Used (typically) for preprocessor commands. | |
2938 | ||
2939 | @item font-lock-negation-char-face | |
2940 | @vindex font-lock-negation-char-face | |
2941 | Used (typically) for easily-overlooked negation characters. | |
2942 | ||
2943 | @item font-lock-warning-face | |
2944 | @vindex font-lock-warning-face | |
2945 | Used (typically) for constructs that are peculiar, or that greatly | |
2946 | change the meaning of other text. For example, this is used for | |
2947 | @samp{;;;###autoload} cookies in Emacs Lisp, and for @code{#error} | |
2948 | directives in C. | |
2949 | @end table | |
2950 | ||
2951 | @node Syntactic Font Lock | |
2952 | @subsection Syntactic Font Lock | |
2953 | @cindex syntactic font lock | |
2954 | ||
2955 | Syntactic fontification uses the syntax table to find comments and | |
2956 | string constants (@pxref{Syntax Tables}). It highlights them using | |
2957 | @code{font-lock-comment-face} and @code{font-lock-string-face} | |
2958 | (@pxref{Faces for Font Lock}), or whatever | |
2959 | @code{font-lock-syntactic-face-function} chooses. There are several | |
2960 | variables that affect syntactic fontification; you should set them by | |
2961 | means of @code{font-lock-defaults} (@pxref{Font Lock Basics}). | |
2962 | ||
2963 | @defvar font-lock-keywords-only | |
2964 | Non-@code{nil} means Font Lock should not do syntactic fontification; | |
2965 | it should only fontify based on @code{font-lock-keywords}. The normal | |
2966 | way for a mode to set this variable to @code{t} is with | |
2967 | @var{keywords-only} in @code{font-lock-defaults}. | |
2968 | @end defvar | |
2969 | ||
2970 | @defvar font-lock-syntax-table | |
2971 | This variable holds the syntax table to use for fontification of | |
2972 | comments and strings. Specify it using @var{syntax-alist} in | |
2973 | @code{font-lock-defaults}. If this is @code{nil}, fontification uses | |
2974 | the buffer's syntax table. | |
2975 | @end defvar | |
2976 | ||
2977 | @defvar font-lock-beginning-of-syntax-function | |
2978 | If this variable is non-@code{nil}, it should be a function to move | |
2979 | point back to a position that is syntactically at ``top level'' and | |
2980 | outside of strings or comments. Font Lock uses this when necessary | |
2981 | to get the right results for syntactic fontification. | |
2982 | ||
2983 | This function is called with no arguments. It should leave point at | |
2984 | the beginning of any enclosing syntactic block. Typical values are | |
2985 | @code{beginning-of-line} (used when the start of the line is known to | |
2986 | be outside a syntactic block), or @code{beginning-of-defun} for | |
2987 | programming modes, or @code{backward-paragraph} for textual modes. | |
2988 | ||
2989 | If the value is @code{nil}, Font Lock uses | |
2990 | @code{syntax-begin-function} to move back outside of any comment, | |
2991 | string, or sexp. This variable is semi-obsolete; we recommend setting | |
2992 | @code{syntax-begin-function} instead. | |
2993 | ||
2994 | Specify this variable using @var{syntax-begin} in | |
2995 | @code{font-lock-defaults}. | |
2996 | @end defvar | |
2997 | ||
2998 | @defvar font-lock-syntactic-face-function | |
2999 | A function to determine which face to use for a given syntactic | |
3000 | element (a string or a comment). The function is called with one | |
3001 | argument, the parse state at point returned by | |
3002 | @code{parse-partial-sexp}, and should return a face. The default | |
3003 | value returns @code{font-lock-comment-face} for comments and | |
3004 | @code{font-lock-string-face} for strings. | |
3005 | ||
3006 | This can be used to highlighting different kinds of strings or | |
3007 | comments differently. It is also sometimes abused together with | |
3008 | @code{font-lock-syntactic-keywords} to highlight constructs that span | |
3009 | multiple lines, but this is too esoteric to document here. | |
3010 | ||
3011 | Specify this variable using @var{other-vars} in | |
3012 | @code{font-lock-defaults}. | |
3013 | @end defvar | |
3014 | ||
3015 | @node Setting Syntax Properties | |
3016 | @subsection Setting Syntax Properties | |
3017 | ||
3018 | Font Lock mode can be used to update @code{syntax-table} properties | |
3019 | automatically (@pxref{Syntax Properties}). This is useful in | |
3020 | languages for which a single syntax table by itself is not sufficient. | |
3021 | ||
3022 | @defvar font-lock-syntactic-keywords | |
3023 | This variable enables and controls updating @code{syntax-table} | |
3024 | properties by Font Lock. Its value should be a list of elements of | |
3025 | this form: | |
3026 | ||
3027 | @example | |
3028 | (@var{matcher} @var{subexp} @var{syntax} @var{override} @var{laxmatch}) | |
3029 | @end example | |
3030 | ||
3031 | The parts of this element have the same meanings as in the corresponding | |
3032 | sort of element of @code{font-lock-keywords}, | |
3033 | ||
3034 | @example | |
3035 | (@var{matcher} @var{subexp} @var{facespec} @var{override} @var{laxmatch}) | |
3036 | @end example | |
3037 | ||
3038 | However, instead of specifying the value @var{facespec} to use for the | |
3039 | @code{face} property, it specifies the value @var{syntax} to use for | |
3040 | the @code{syntax-table} property. Here, @var{syntax} can be a string | |
3041 | (as taken by @code{modify-syntax-entry}), a syntax table, a cons cell | |
3042 | (as returned by @code{string-to-syntax}), or an expression whose value | |
3043 | is one of those two types. @var{override} cannot be @code{prepend} or | |
3044 | @code{append}. | |
3045 | ||
3046 | For example, an element of the form: | |
3047 | ||
3048 | @example | |
3049 | ("\\$\\(#\\)" 1 ".") | |
3050 | @end example | |
3051 | ||
3052 | highlights syntactically a hash character when following a dollar | |
3053 | character, with a SYNTAX of @code{"."} (meaning punctuation syntax). | |
3054 | Assuming that the buffer syntax table specifies hash characters to | |
3055 | have comment start syntax, the element will only highlight hash | |
3056 | characters that do not follow dollar characters as comments | |
3057 | syntactically. | |
3058 | ||
3059 | An element of the form: | |
3060 | ||
3061 | @example | |
3062 | ("\\('\\).\\('\\)" | |
3063 | (1 "\"") | |
3064 | (2 "\"")) | |
3065 | @end example | |
3066 | ||
3067 | highlights syntactically both single quotes which surround a single | |
3068 | character, with a SYNTAX of @code{"\""} (meaning string quote syntax). | |
3069 | Assuming that the buffer syntax table does not specify single quotes | |
3070 | to have quote syntax, the element will only highlight single quotes of | |
3071 | the form @samp{'@var{c}'} as strings syntactically. Other forms, such | |
3072 | as @samp{foo'bar} or @samp{'fubar'}, will not be highlighted as | |
3073 | strings. | |
3074 | ||
3075 | Major modes normally set this variable with @var{other-vars} in | |
3076 | @code{font-lock-defaults}. | |
3077 | @end defvar | |
3078 | ||
3079 | @node Multiline Font Lock | |
3080 | @subsection Multiline Font Lock Constructs | |
3081 | @cindex multiline font lock | |
3082 | ||
3083 | Normally, elements of @code{font-lock-keywords} should not match | |
3084 | across multiple lines; that doesn't work reliably, because Font Lock | |
3085 | usually scans just part of the buffer, and it can miss a multi-line | |
3086 | construct that crosses the line boundary where the scan starts. (The | |
3087 | scan normally starts at the beginning of a line.) | |
3088 | ||
3089 | Making elements that match multiline constructs work properly has | |
3090 | two aspects: correct @emph{identification} and correct | |
3091 | @emph{rehighlighting}. The first means that Font Lock finds all | |
3092 | multiline constructs. The second means that Font Lock will correctly | |
3093 | rehighlight all the relevant text when a multiline construct is | |
3094 | changed---for example, if some of the text that was previously part of | |
3095 | a multiline construct ceases to be part of it. The two aspects are | |
3096 | closely related, and often getting one of them to work will appear to | |
3097 | make the other also work. However, for reliable results you must | |
3098 | attend explicitly to both aspects. | |
3099 | ||
3100 | There are three ways to ensure correct identification of multiline | |
3101 | constructs: | |
3102 | ||
3103 | @itemize | |
3104 | @item | |
3105 | Add a function to @code{font-lock-extend-region-functions} that does | |
3106 | the @emph{identification} and extends the scan so that the scanned | |
3107 | text never starts or ends in the middle of a multiline construct. | |
3108 | @item | |
3109 | Use the @code{font-lock-fontify-region-function} hook similarly to | |
3110 | extend the scan so that the scanned text never starts or ends in the | |
3111 | middle of a multiline construct. | |
3112 | @item | |
3113 | Somehow identify the multiline construct right when it gets inserted | |
3114 | into the buffer (or at any point after that but before font-lock | |
3115 | tries to highlight it), and mark it with a @code{font-lock-multiline} | |
3116 | which will instruct font-lock not to start or end the scan in the | |
3117 | middle of the construct. | |
3118 | @end itemize | |
3119 | ||
3120 | There are three ways to do rehighlighting of multiline constructs: | |
3121 | ||
3122 | @itemize | |
3123 | @item | |
3124 | Place a @code{font-lock-multiline} property on the construct. This | |
3125 | will rehighlight the whole construct if any part of it is changed. In | |
3126 | some cases you can do this automatically by setting the | |
3127 | @code{font-lock-multiline} variable, which see. | |
3128 | @item | |
3129 | Make sure @code{jit-lock-contextually} is set and rely on it doing its | |
3130 | job. This will only rehighlight the part of the construct that | |
3131 | follows the actual change, and will do it after a short delay. | |
3132 | This only works if the highlighting of the various parts of your | |
3133 | multiline construct never depends on text in subsequent lines. | |
3134 | Since @code{jit-lock-contextually} is activated by default, this can | |
3135 | be an attractive solution. | |
3136 | @item | |
3137 | Place a @code{jit-lock-defer-multiline} property on the construct. | |
3138 | This works only if @code{jit-lock-contextually} is used, and with the | |
3139 | same delay before rehighlighting, but like @code{font-lock-multiline}, | |
3140 | it also handles the case where highlighting depends on | |
3141 | subsequent lines. | |
3142 | @end itemize | |
3143 | ||
3144 | @menu | |
fe42c16a | 3145 | * Font Lock Multiline:: Marking multiline chunks with a text property. |
b8d4c8d0 GM |
3146 | * Region to Fontify:: Controlling which region gets refontified |
3147 | after a buffer change. | |
3148 | @end menu | |
3149 | ||
3150 | @node Font Lock Multiline | |
3151 | @subsubsection Font Lock Multiline | |
3152 | ||
3153 | One way to ensure reliable rehighlighting of multiline Font Lock | |
3154 | constructs is to put on them the text property @code{font-lock-multiline}. | |
3155 | It should be present and non-@code{nil} for text that is part of a | |
3156 | multiline construct. | |
3157 | ||
3158 | When Font Lock is about to highlight a range of text, it first | |
3159 | extends the boundaries of the range as necessary so that they do not | |
3160 | fall within text marked with the @code{font-lock-multiline} property. | |
3161 | Then it removes any @code{font-lock-multiline} properties from the | |
3162 | range, and highlights it. The highlighting specification (mostly | |
3163 | @code{font-lock-keywords}) must reinstall this property each time, | |
3164 | whenever it is appropriate. | |
3165 | ||
3166 | @strong{Warning:} don't use the @code{font-lock-multiline} property | |
3167 | on large ranges of text, because that will make rehighlighting slow. | |
3168 | ||
3169 | @defvar font-lock-multiline | |
3170 | If the @code{font-lock-multiline} variable is set to @code{t}, Font | |
3171 | Lock will try to add the @code{font-lock-multiline} property | |
3172 | automatically on multiline constructs. This is not a universal | |
3173 | solution, however, since it slows down Font Lock somewhat. It can | |
3174 | miss some multiline constructs, or make the property larger or smaller | |
3175 | than necessary. | |
3176 | ||
3177 | For elements whose @var{matcher} is a function, the function should | |
3178 | ensure that submatch 0 covers the whole relevant multiline construct, | |
3179 | even if only a small subpart will be highlighted. It is often just as | |
3180 | easy to add the @code{font-lock-multiline} property by hand. | |
3181 | @end defvar | |
3182 | ||
3183 | The @code{font-lock-multiline} property is meant to ensure proper | |
3184 | refontification; it does not automatically identify new multiline | |
3185 | constructs. Identifying the requires that Font-Lock operate on large | |
3186 | enough chunks at a time. This will happen by accident on many cases, | |
3187 | which may give the impression that multiline constructs magically work. | |
3188 | If you set the @code{font-lock-multiline} variable non-@code{nil}, | |
3189 | this impression will be even stronger, since the highlighting of those | |
3190 | constructs which are found will be properly updated from then on. | |
3191 | But that does not work reliably. | |
3192 | ||
3193 | To find multiline constructs reliably, you must either manually | |
3194 | place the @code{font-lock-multiline} property on the text before | |
3195 | Font-Lock looks at it, or use | |
3196 | @code{font-lock-fontify-region-function}. | |
3197 | ||
3198 | @node Region to Fontify | |
3199 | @subsubsection Region to Fontify after a Buffer Change | |
3200 | ||
3201 | When a buffer is changed, the region that Font Lock refontifies is | |
3202 | by default the smallest sequence of whole lines that spans the change. | |
3203 | While this works well most of the time, sometimes it doesn't---for | |
3204 | example, when a change alters the syntactic meaning of text on an | |
3205 | earlier line. | |
3206 | ||
3207 | You can enlarge (or even reduce) the region to fontify by setting | |
3208 | one the following variables: | |
3209 | ||
3210 | @defvar font-lock-extend-after-change-region-function | |
3211 | This buffer-local variable is either @code{nil} or a function for | |
3212 | Font-Lock to call to determine the region to scan and fontify. | |
3213 | ||
3214 | The function is given three parameters, the standard @var{beg}, | |
3215 | @var{end}, and @var{old-len} from after-change-functions | |
3216 | (@pxref{Change Hooks}). It should return either a cons of the | |
3217 | beginning and end buffer positions (in that order) of the region to | |
3218 | fontify, or @code{nil} (which means choose the region in the standard | |
3219 | way). This function needs to preserve point, the match-data, and the | |
3220 | current restriction. The region it returns may start or end in the | |
3221 | middle of a line. | |
3222 | ||
3223 | Since this function is called after every buffer change, it should be | |
3224 | reasonably fast. | |
3225 | @end defvar | |
3226 | ||
5dcb4c4e SM |
3227 | @node Auto-Indentation |
3228 | @section Auto-indention of code | |
3229 | ||
3230 | For programming languages, an important feature of a major mode is to | |
3231 | provide automatic indentation. This is controlled in Emacs by | |
3232 | @code{indent-line-function} (@pxref{Mode-Specific Indent}). | |
3233 | Writing a good indentation function can be difficult and to a large | |
3234 | extent it is still a black art. | |
3235 | ||
3236 | Many major mode authors will start by writing a simple indentation | |
3237 | function that works for simple cases, for example by comparing with the | |
3238 | indentation of the previous text line. For most programming languages | |
3239 | that are not really line-based, this tends to scale very poorly: | |
3240 | improving such a function to let it handle more diverse situations tends | |
3241 | to become more and more difficult, resulting in the end with a large, | |
3242 | complex, unmaintainable indentation function which nobody dares to touch. | |
3243 | ||
3244 | A good indentation function will usually need to actually parse the | |
3245 | text, according to the syntax of the language. Luckily, it is not | |
3246 | necessary to parse the text in as much detail as would be needed | |
3247 | for a compiler, but on the other hand, the parser embedded in the | |
3248 | indentation code will want to be somewhat friendly to syntactically | |
3249 | incorrect code. | |
3250 | ||
3251 | Good maintainable indentation functions usually fall into 2 categories: | |
3252 | either parsing forward from some ``safe'' starting point until the | |
3253 | position of interest, or parsing backward from the position of interest. | |
3254 | Neither of the two is a clearly better choice than the other: parsing | |
3255 | backward is often more difficult than parsing forward because | |
3256 | programming languages are designed to be parsed forward, but for the | |
3257 | purpose of indentation it has the advantage of not needing to | |
3258 | guess a ``safe'' starting point, and it generally enjoys the property | |
3259 | that only a minimum of text will be analyzed to decide the indentation | |
3260 | of a line, so indentation will tend to be unaffected by syntax errors in | |
3261 | some earlier unrelated piece of code. Parsing forward on the other hand | |
3262 | is usually easier and has the advantage of making it possible to | |
3263 | reindent efficiently a whole region at a time, with a single parse. | |
3264 | ||
3265 | Rather than write your own indentation function from scratch, it is | |
3266 | often preferable to try and reuse some existing ones or to rely | |
3267 | on a generic indentation engine. There are sadly few such | |
3268 | engines. The CC-mode indentation code (used with C, C++, Java, Awk | |
3269 | and a few other such modes) has been made more generic over the years, | |
3270 | so if your language seems somewhat similar to one of those languages, | |
3271 | you might try to use that engine. @c FIXME: documentation? | |
3272 | Another one is SMIE which takes an approach in the spirit | |
3273 | of Lisp sexps and adapts it to non-Lisp languages. | |
3274 | ||
3275 | @menu | |
3276 | * SMIE:: A simple minded indentation engine | |
3277 | @end menu | |
3278 | ||
3279 | @node SMIE | |
3280 | @subsection Simple Minded Indentation Engine | |
3281 | ||
3282 | SMIE is a package that provides a generic navigation and indentation | |
3283 | engine. Based on a very simple parser using an ``operator precedence | |
3284 | grammar'', it lets major modes extend the sexp-based navigation of Lisp | |
3285 | to non-Lisp languages as well as provide a simple to use but reliable | |
3286 | auto-indentation. | |
3287 | ||
3288 | Operator precedence grammar is a very primitive technology for parsing | |
3289 | compared to some of the more common techniques used in compilers. | |
3290 | It has the following characteristics: its parsing power is very limited, | |
3291 | and it is largely unable to detect syntax errors, but it has the | |
3292 | advantage of being algorithmically efficient and able to parse forward | |
3293 | just as well as backward. In practice that means that SMIE can use it | |
3294 | for indentation based on backward parsing, that it can provide both | |
3295 | @code{forward-sexp} and @code{backward-sexp} functionality, and that it | |
3296 | will naturally work on syntactically incorrect code without any extra | |
3297 | effort. The downside is that it also means that most programming | |
3298 | languages cannot be parsed correctly using SMIE, at least not without | |
3299 | resorting to some special tricks (@pxref{SMIE Tricks}). | |
3300 | ||
3301 | @menu | |
3302 | * SMIE setup:: SMIE setup and features | |
3303 | * Operator Precedence Grammars:: A very simple parsing technique | |
3304 | * SMIE Grammar:: Defining the grammar of a language | |
3305 | * SMIE Lexer:: Defining tokens | |
3306 | * SMIE Tricks:: Working around the parser's limitations | |
3307 | * SMIE Indentation:: Specifying indentation rules | |
3308 | * SMIE Indentation Helpers:: Helper functions for indentation rules | |
3309 | * SMIE Indentation Example:: Sample indentation rules | |
3310 | @end menu | |
3311 | ||
3312 | @node SMIE setup | |
3313 | @subsubsection SMIE Setup and Features | |
3314 | ||
3315 | SMIE is meant to be a one-stop shop for structural navigation and | |
3316 | various other features which rely on the syntactic structure of code, in | |
3317 | particular automatic indentation. The main entry point is | |
3318 | @code{smie-setup} which is a function typically called while setting | |
3319 | up a major mode. | |
3320 | ||
3321 | @defun smie-setup grammar rules-function &rest keywords | |
3322 | Setup SMIE navigation and indentation. | |
3323 | @var{grammar} is a grammar table generated by @code{smie-prec2->grammar}. | |
3324 | @var{rules-function} is a set of indentation rules for use on | |
3325 | @code{smie-rules-function}. | |
3326 | @var{keywords} are additional arguments, which can include the following | |
3327 | keywords: | |
3328 | @itemize | |
3329 | @item | |
3330 | @code{:forward-token} @var{fun}: Specify the forward lexer to use. | |
3331 | @item | |
3332 | @code{:backward-token} @var{fun}: Specify the backward lexer to use. | |
3333 | @end itemize | |
3334 | @end defun | |
3335 | ||
3336 | Calling this function is sufficient to make commands such as | |
3337 | @code{forward-sexp}, @code{backward-sexp}, and @code{transpose-sexps} be | |
3338 | able to properly handle structural elements other than just the paired | |
3339 | parentheses already handled by syntax tables. For example, if the | |
3340 | provided grammar is precise enough, @code{transpose-sexps} can correctly | |
3341 | transpose the two arguments of a @code{+} operator, taking into account | |
3342 | the precedence rules of the language. | |
3343 | ||
3344 | Calling `smie-setup' is also sufficient to make TAB indentation work in | |
3345 | the expected way, and provides some commands that you can bind in the | |
3346 | major mode keymap. | |
3347 | ||
3348 | @deffn Command smie-close-block | |
3349 | This command closes the most recently opened (and not yet closed) block. | |
3350 | @end deffn | |
3351 | ||
3352 | @deffn Command smie-down-list &optional arg | |
3353 | This command is like @code{down-list} but it also pays attention to | |
3354 | nesting of tokens other than parentheses, such as @code{begin...end}. | |
3355 | @end deffn | |
3356 | ||
3357 | @node Operator Precedence Grammars | |
3358 | @subsubsection Operator Precedence Grammars | |
3359 | ||
3360 | SMIE's precedence grammars simply give to each token a pair of | |
3361 | precedences: the left-precedence and the right-precedence. We say | |
3362 | @code{T1 < T2} if the right-precedence of token @code{T1} is less than | |
3363 | the left-precedence of token @code{T2}. A good way to read this | |
3364 | @code{<} is as a kind of parenthesis: if we find @code{... T1 something | |
3365 | T2 ...} then that should be parsed as @code{... T1 (something T2 ...} | |
3366 | rather than as @code{... T1 something) T2 ...}. The latter | |
3367 | interpretation would be the case if we had @code{T1 > T2}. If we have | |
3368 | @code{T1 = T2}, it means that token T2 follows token T1 in the same | |
3369 | syntactic construction, so typically we have @code{"begin" = "end"}. | |
3370 | Such pairs of precedences are sufficient to express left-associativity | |
3371 | or right-associativity of infix operators, nesting of tokens like | |
3372 | parentheses and many other cases. | |
3373 | ||
3374 | @c ¡Let's leave this undocumented to leave it more open for change! | |
3375 | @c @defvar smie-grammar | |
3376 | @c The value of this variable is an alist specifying the left and right | |
3377 | @c precedence of each token. It is meant to be initialized by using one of | |
3378 | @c the functions below. | |
3379 | @c @end defvar | |
3380 | ||
3381 | @defun smie-prec2->grammar table | |
3382 | This function takes a @emph{prec2} grammar @var{table} and returns an | |
3383 | alist suitable for use in @code{smie-setup}. The @emph{prec2} | |
3384 | @var{table} is itself meant to be built by one of the functions below. | |
3385 | @end defun | |
3386 | ||
3387 | @defun smie-merge-prec2s &rest tables | |
3388 | This function takes several @emph{prec2} @var{tables} and merges them | |
3389 | into a new @emph{prec2} table. | |
3390 | @end defun | |
3391 | ||
3392 | @defun smie-precs->prec2 precs | |
3393 | This function builds a @emph{prec2} table from a table of precedences | |
3394 | @var{precs}. @var{precs} should be a list, sorted by precedence (for | |
3395 | example @code{"+"} will come before @code{"*"}), of elements of the form | |
3396 | @code{(@var{assoc} @var{op} ...)}, where each @var{op} is a token that | |
3397 | acts as an operator; @var{assoc} is their associativity, which can be | |
3398 | either @code{left}, @code{right}, @code{assoc}, or @code{nonassoc}. | |
3399 | All operators in a given element share the same precedence level | |
3400 | and associativity. | |
3401 | @end defun | |
3402 | ||
3403 | @defun smie-bnf->prec2 bnf &rest resolvers | |
3404 | This function lets you specify the grammar using a BNF notation. | |
3405 | It accepts a @var{bnf} description of the grammar along with a set of | |
3406 | conflict resolution rules @var{resolvers}, and | |
3407 | returns a @emph{prec2} table. | |
3408 | ||
3409 | @var{bnf} is a list of nonterminal definitions of the form | |
3410 | @code{(@var{nonterm} @var{rhs1} @var{rhs2} ...)} where each @var{rhs} | |
3411 | is a (non-empty) list of terminals (aka tokens) or non-terminals. | |
3412 | ||
3413 | Not all grammars are accepted: | |
3414 | @itemize | |
3415 | @item | |
3416 | An @var{rhs} cannot be an empty list (an empty list is never needed, | |
3417 | since SMIE allows all non-terminals to match the empty string anyway). | |
3418 | @item | |
3419 | An @var{rhs} cannot have 2 consecutive non-terminals: each pair of | |
3420 | non-terminals needs to be separated by a terminal (aka token). | |
3421 | This is a fundamental limitation of operator precedence grammars. | |
3422 | @end itemize | |
3423 | ||
3424 | Additionally, conflicts can occur: | |
3425 | @itemize | |
3426 | @item | |
3427 | The returned @emph{prec2} table holds constraints between pairs of tokens, and | |
3428 | for any given pair only one constraint can be present: T1 < T2, | |
3429 | T1 = T2, or T1 > T2. | |
3430 | @item | |
3431 | A token can be an @code{opener} (something similar to an open-paren), | |
3432 | a @code{closer} (like a close-paren), or @code{neither} of the two | |
3433 | (e.g. an infix operator, or an inner token like @code{"else"}). | |
3434 | @end itemize | |
3435 | ||
3436 | Precedence conflicts can be resolved via @var{resolvers}, which | |
3437 | is a list of @emph{precs} tables (see @code{smie-precs->prec2}): for | |
3438 | each precedence conflict, if those @code{precs} tables | |
3439 | specify a particular constraint, then the conflict is resolved by using | |
3440 | this constraint instead, else a conflict is reported and one of the | |
3441 | conflicting constraints is picked arbitrarily and the others are | |
3442 | simply ignored. | |
3443 | @end defun | |
3444 | ||
3445 | @node SMIE Grammar | |
3446 | @subsubsection Defining the Grammar of a Language | |
3447 | ||
3448 | The usual way to define the SMIE grammar of a language is by | |
3449 | defining a new global variable that holds the precedence table by | |
3450 | giving a set of BNF rules. | |
3451 | For example, the grammar definition for a small Pascal-like language | |
3452 | could look like: | |
3453 | @example | |
3454 | @group | |
3455 | (require 'smie) | |
3456 | (defvar sample-smie-grammar | |
3457 | (smie-prec2->grammar | |
3458 | (smie-bnf->prec2 | |
3459 | @end group | |
3460 | @group | |
3461 | '((id) | |
3462 | (inst ("begin" insts "end") | |
3463 | ("if" exp "then" inst "else" inst) | |
3464 | (id ":=" exp) | |
3465 | (exp)) | |
3466 | (insts (insts ";" insts) (inst)) | |
3467 | (exp (exp "+" exp) | |
3468 | (exp "*" exp) | |
3469 | ("(" exps ")")) | |
3470 | (exps (exps "," exps) (exp))) | |
3471 | @end group | |
3472 | @group | |
3473 | '((assoc ";")) | |
3474 | '((assoc ",")) | |
3475 | '((assoc "+") (assoc "*"))))) | |
3476 | @end group | |
3477 | @end example | |
3478 | ||
3479 | @noindent | |
3480 | A few things to note: | |
3481 | ||
3482 | @itemize | |
3483 | @item | |
3484 | The above grammar does not explicitly mention the syntax of function | |
3485 | calls: SMIE will automatically allow any sequence of sexps, such as | |
3486 | identifiers, balanced parentheses, or @code{begin ... end} blocks | |
3487 | to appear anywhere anyway. | |
3488 | @item | |
3489 | The grammar category @code{id} has no right hand side: this does not | |
3490 | mean that it can match only the empty string, since as mentioned any | |
3491 | sequence of sexps can appear anywhere anyway. | |
3492 | @item | |
3493 | Because non terminals cannot appear consecutively in the BNF grammar, it | |
3494 | is difficult to correctly handle tokens that act as terminators, so the | |
3495 | above grammar treats @code{";"} as a statement @emph{separator} instead, | |
3496 | which SMIE can handle very well. | |
3497 | @item | |
3498 | Separators used in sequences (such as @code{","} and @code{";"} above) | |
3499 | are best defined with BNF rules such as @code{(foo (foo "separator" foo) ...)} | |
3500 | which generate precedence conflicts which are then resolved by giving | |
3501 | them an explicit @code{(assoc "separator")}. | |
3502 | @item | |
3503 | The @code{("(" exps ")")} rule was not needed to pair up parens, since | |
3504 | SMIE will pair up any characters that are marked as having paren syntax | |
3505 | in the syntax table. What this rule does instead (together with the | |
3506 | definition of @code{exps}) is to make it clear that @code{","} should | |
3507 | not appear outside of parentheses. | |
3508 | @item | |
3509 | Rather than have a single @emph{precs} table to resolve conflicts, it is | |
3510 | preferable to have several tables, so as to let the BNF part of the | |
3511 | grammar specify relative precedences where possible. | |
3512 | @item | |
3513 | Unless there is a very good reason to prefer @code{left} or | |
3514 | @code{right}, it is usually preferable to mark operators as associative, | |
3515 | using @code{assoc}. For that reason @code{"+"} and @code{"*"} are | |
3516 | defined above as @code{assoc}, although the language defines them | |
3517 | formally as left associative. | |
3518 | @end itemize | |
3519 | ||
3520 | @node SMIE Lexer | |
3521 | @subsubsection Defining Tokens | |
3522 | ||
3523 | SMIE comes with a predefined lexical analyzer which uses syntax tables | |
3524 | in the following way: any sequence of characters that have word or | |
3525 | symbol syntax is considered a token, and so is any sequence of | |
3526 | characters that have punctuation syntax. This default lexer is | |
3527 | often a good starting point but is rarely actually correct for any given | |
3528 | language. For example, it will consider @code{"2,+3"} to be composed | |
3529 | of 3 tokens: @code{"2"}, @code{",+"}, and @code{"3"}. | |
3530 | ||
3531 | To describe the lexing rules of your language to SMIE, you need | |
3532 | 2 functions, one to fetch the next token, and another to fetch the | |
3533 | previous token. Those functions will usually first skip whitespace and | |
3534 | comments and then look at the next chunk of text to see if it | |
3535 | is a special token. If so it should skip the token and | |
3536 | return a description of this token. Usually this is simply the string | |
3537 | extracted from the buffer, but it can be anything you want. | |
3538 | For example: | |
3539 | @example | |
3540 | @group | |
3541 | (defvar sample-keywords-regexp | |
3542 | (regexp-opt '("+" "*" "," ";" ">" ">=" "<" "<=" ":=" "="))) | |
3543 | @end group | |
3544 | @group | |
3545 | (defun sample-smie-forward-token () | |
3546 | (forward-comment (point-max)) | |
3547 | (cond | |
3548 | ((looking-at sample-keywords-regexp) | |
3549 | (goto-char (match-end 0)) | |
3550 | (match-string-no-properties 0)) | |
3551 | (t (buffer-substring-no-properties | |
3552 | (point) | |
3553 | (progn (skip-syntax-forward "w_") | |
3554 | (point)))))) | |
3555 | @end group | |
3556 | @group | |
3557 | (defun sample-smie-backward-token () | |
3558 | (forward-comment (- (point))) | |
3559 | (cond | |
3560 | ((looking-back sample-keywords-regexp (- (point) 2) t) | |
3561 | (goto-char (match-beginning 0)) | |
3562 | (match-string-no-properties 0)) | |
3563 | (t (buffer-substring-no-properties | |
3564 | (point) | |
3565 | (progn (skip-syntax-backward "w_") | |
3566 | (point)))))) | |
3567 | @end group | |
3568 | @end example | |
3569 | ||
3570 | Notice how those lexers return the empty string when in front of | |
3571 | parentheses. This is because SMIE automatically takes care of the | |
3572 | parentheses defined in the syntax table. More specifically if the lexer | |
3573 | returns nil or an empty string, SMIE tries to handle the corresponding | |
3574 | text as a sexp according to syntax tables. | |
3575 | ||
3576 | @node SMIE Tricks | |
3577 | @subsubsection Living With a Weak Parser | |
3578 | ||
3579 | The parsing technique used by SMIE does not allow tokens to behave | |
3580 | differently in different contexts. For most programming languages, this | |
3581 | manifests itself by precedence conflicts when converting the | |
3582 | BNF grammar. | |
3583 | ||
3584 | Sometimes, those conflicts can be worked around by expressing the | |
3585 | grammar slightly differently. For example, for Modula-2 it might seem | |
3586 | natural to have a BNF grammar that looks like this: | |
3587 | ||
3588 | @example | |
3589 | ... | |
3590 | (inst ("IF" exp "THEN" insts "ELSE" insts "END") | |
3591 | ("CASE" exp "OF" cases "END") | |
3592 | ...) | |
3593 | (cases (cases "|" cases) (caselabel ":" insts) ("ELSE" insts)) | |
3594 | ... | |
3595 | @end example | |
3596 | ||
3597 | But this will create conflicts for @code{"ELSE"}: on the one hand, the | |
3598 | IF rule implies (among many other things) that @code{"ELSE" = "END"}; | |
3599 | but on the other hand, since @code{"ELSE"} appears within @code{cases}, | |
3600 | which appears left of @code{"END"}, we also have @code{"ELSE" > "END"}. | |
3601 | We can solve the conflict either by using: | |
3602 | @example | |
3603 | ... | |
3604 | (inst ("IF" exp "THEN" insts "ELSE" insts "END") | |
3605 | ("CASE" exp "OF" cases "END") | |
3606 | ("CASE" exp "OF" cases "ELSE" insts "END") | |
3607 | ...) | |
3608 | (cases (cases "|" cases) (caselabel ":" insts)) | |
3609 | ... | |
3610 | @end example | |
3611 | or | |
3612 | @example | |
3613 | ... | |
3614 | (inst ("IF" exp "THEN" else "END") | |
3615 | ("CASE" exp "OF" cases "END") | |
3616 | ...) | |
3617 | (else (insts "ELSE" insts)) | |
3618 | (cases (cases "|" cases) (caselabel ":" insts) (else)) | |
3619 | ... | |
3620 | @end example | |
3621 | ||
3622 | Reworking the grammar to try and solve conflicts has its downsides, tho, | |
3623 | because SMIE assumes that the grammar reflects the logical structure of | |
3624 | the code, so it is preferable to keep the BNF closer to the intended | |
3625 | abstract syntax tree. | |
3626 | ||
3627 | Other times, after careful consideration you may conclude that those | |
3628 | conflicts are not serious and simply resolve them via the | |
3629 | @var{resolvers} argument of @code{smie-bnf->prec2}. Usually this is | |
3630 | because the grammar is simply ambiguous: the conflict does not affect | |
3631 | the set of programs described by the grammar, but only the way those | |
3632 | programs are parsed. This is typically the case for separators and | |
3633 | associative infix operators, where you want to add a resolver like | |
3634 | @code{'((assoc "|"))}. Another case where this can happen is for the | |
3635 | classic @emph{dangling else} problem, where you will use @code{'((assoc | |
3636 | "else" "then"))}. It can also happen for cases where the conflict is | |
3637 | real and cannot really be resolved, but it is unlikely to pose a problem | |
3638 | in practice. | |
3639 | ||
3640 | Finally, in many cases some conflicts will remain despite all efforts to | |
3641 | restructure the grammar. Do not despair: while the parser cannot be | |
3642 | made more clever, you can make the lexer as smart as you want. So, the | |
3643 | solution is then to look at the tokens involved in the conflict and to | |
3644 | split one of those tokens into 2 (or more) different tokens. E.g. if | |
3645 | the grammar needs to distinguish between two incompatible uses of the | |
3646 | token @code{"begin"}, make the lexer return different tokens (say | |
3647 | @code{"begin-fun"} and @code{"begin-plain"}) depending on which kind of | |
3648 | @code{"begin"} it finds. This pushes the work of distinguishing the | |
3649 | different cases to the lexer, which will thus have to look at the | |
3650 | surrounding text to find ad-hoc clues. | |
3651 | ||
3652 | @node SMIE Indentation | |
3653 | @subsubsection Specifying Indentation Rules | |
3654 | ||
3655 | Based on the provided grammar, SMIE will be able to provide automatic | |
3656 | indentation without any extra effort. But in practice, this default | |
3657 | indentation style will probably not be good enough. You will want to | |
3658 | tweak it in many different cases. | |
3659 | ||
3660 | SMIE indentation is based on the idea that indentation rules should be | |
3661 | as local as possible. To this end, it relies on the idea of | |
3662 | @emph{virtual} indentation, which is the indentation that a particular | |
3663 | program point would have if it were at the beginning of a line. | |
3664 | Of course, if that program point is indeed at the beginning of a line, | |
3665 | its virtual indentation is its current indentation. But if not, then | |
3666 | SMIE uses the indentation algorithm to compute the virtual indentation | |
3667 | of that point. Now in practice, the virtual indentation of a program | |
3668 | point does not have to be identical to the indentation it would have if | |
3669 | we inserted a newline before it. To see how this works, the SMIE rule | |
3670 | for indentation after a @code{@{} in C does not care whether the | |
3671 | @code{@{} is standing on a line of its own or is at the end of the | |
3672 | preceding line. Instead, these different cases are handled in the | |
3673 | indentation rule that decides how to indent before a @code{@{}. | |
3674 | ||
3675 | Another important concept is the notion of @emph{parent}: The | |
3676 | @emph{parent} of a token, is the head token of the nearest enclosing | |
3677 | syntactic construct. For example, the parent of an @code{else} is the | |
3678 | @code{if} to which it belongs, and the parent of an @code{if}, in turn, | |
3679 | is the lead token of the surrounding construct. The command | |
3680 | @code{backward-sexp} jumps from a token to its parent, but there are | |
3681 | some caveats: for @emph{openers} (tokens which start a construct, like | |
3682 | @code{if}), you need to start with point before the token, while for | |
3683 | others you need to start with point after the token. | |
3684 | @code{backward-sexp} stops with point before the parent token if that is | |
3685 | the @emph{opener} of the token of interest, and otherwise it stops with | |
3686 | point after the parent token. | |
3687 | ||
3688 | SMIE indentation rules are specified using a function that takes two | |
3689 | arguments @var{method} and @var{arg} where the meaning of @var{arg} and the | |
3690 | expected return value depend on @var{method}. | |
3691 | ||
3692 | @var{method} can be: | |
3693 | @itemize | |
3694 | @item | |
3695 | @code{:after}, in which case @var{arg} is a token and the function | |
3696 | should return the @var{offset} to use for indentation after @var{arg}. | |
3697 | @item | |
3698 | @code{:before}, in which case @var{arg} is a token and the function | |
3699 | should return the @var{offset} to use to indent @var{arg} itself. | |
3700 | @item | |
3701 | @code{:elem}, in which case the function should return either the offset | |
3702 | to use to indent function arguments (if @var{arg} is the symbol | |
3703 | @code{arg}) or the basic indentation step (if @var{arg} is the symbol | |
3704 | @code{basic}). | |
3705 | @item | |
3706 | @code{:list-intro}, in which case @var{arg} is a token and the function | |
3707 | should return non-@code{nil} if the token is followed by a list of | |
3708 | expressions (not separated by any token) rather than an expression. | |
3709 | @end itemize | |
3710 | ||
3711 | When @var{arg} is a token, the function is called with point just before | |
3712 | that token. A return value of nil always means to fallback on the | |
3713 | default behavior, so the function should return nil for arguments it | |
3714 | does not expect. | |
3715 | ||
3716 | @var{offset} can be: | |
3717 | @itemize | |
3718 | @item | |
3719 | @code{nil}: use the default indentation rule. | |
3720 | @item | |
3721 | @code{(column . @var{column})}: indent to column @var{column}. | |
3722 | @item | |
3723 | @var{number}: offset by @var{number}, relative to a base token which is | |
3724 | the current token for @code{:after} and its parent for @code{:before}. | |
3725 | @end itemize | |
3726 | ||
3727 | @node SMIE Indentation Helpers | |
3728 | @subsubsection Helper Functions for Indentation Rules | |
3729 | ||
3730 | SMIE provides various functions designed specifically for use in the | |
3731 | indentation rules function (several of those functions break if used in | |
3732 | another context). These functions all start with the prefix | |
3733 | @code{smie-rule-}. | |
3734 | ||
3735 | @defun smie-rule-bolp | |
3736 | Return non-@code{nil} if the current token is the first on the line. | |
3737 | @end defun | |
3738 | ||
3739 | @defun smie-rule-hanging-p | |
3740 | Return non-@code{nil} if the current token is @emph{hanging}. | |
3741 | A token is @emph{hanging} if it is the last token on the line | |
3742 | and if it is preceded by other tokens: a lone token on a line is not | |
3743 | hanging. | |
3744 | @end defun | |
3745 | ||
3746 | @defun smie-rule-next-p &rest tokens | |
3747 | Return non-@code{nil} if the next token is among @var{tokens}. | |
3748 | @end defun | |
3749 | ||
3750 | @defun smie-rule-prev-p &rest tokens | |
3751 | Return non-@code{nil} if the previous token is among @var{tokens}. | |
3752 | @end defun | |
3753 | ||
3754 | @defun smie-rule-parent-p &rest parents | |
3755 | Return non-@code{nil} if the current token's parent is among @var{parents}. | |
3756 | @end defun | |
3757 | ||
3758 | @defun smie-rule-sibling-p | |
3759 | Return non-nil if the current token's parent is actually a sibling. | |
3760 | This is the case for example when the parent of a @code{","} is just the | |
3761 | previous @code{","}. | |
3762 | @end defun | |
3763 | ||
3764 | @defun smie-rule-parent &optional offset | |
3765 | Return the proper offset to align the current token with the parent. | |
3766 | If non-@code{nil}, @var{offset} should be an integer giving an | |
3767 | additional offset to apply. | |
3768 | @end defun | |
3769 | ||
3770 | @defun smie-rule-separator method | |
3771 | Indent current token as a @emph{separator}. | |
3772 | ||
3773 | By @emph{separator}, we mean here a token whose sole purpose is to | |
3774 | separate various elements within some enclosing syntactic construct, and | |
3775 | which does not have any semantic significance in itself (i.e. it would | |
3776 | typically not exist as a node in an abstract syntax tree). | |
3777 | ||
3778 | Such a token is expected to have an associative syntax and be closely | |
3779 | tied to its syntactic parent. Typical examples are @code{","} in lists | |
3780 | of arguments (enclosed inside parentheses), or @code{";"} in sequences | |
3781 | of instructions (enclosed in a @code{@{...@}} or @code{begin...end} | |
3782 | block). | |
3783 | ||
3784 | @var{method} should be the method name that was passed to | |
3785 | `smie-rules-function'. | |
3786 | @end defun | |
3787 | ||
3788 | @node SMIE Indentation Example | |
3789 | @subsubsection Sample Indentation Rules | |
3790 | ||
3791 | Here is an example of an indentation function: | |
3792 | ||
3793 | @example | |
3794 | (eval-when-compile (require 'cl)) ;For the `case' macro. | |
3795 | (defun sample-smie-rules (kind token) | |
3796 | (case kind | |
3797 | (:elem (case token | |
3798 | (basic sample-indent-basic))) | |
3799 | (:after | |
3800 | (cond | |
3801 | ((equal token ",") (smie-rule-separator kind)) | |
3802 | ((equal token ":=") sample-indent-basic))) | |
3803 | (:before | |
3804 | (cond | |
3805 | ((equal token ",") (smie-rule-separator kind)) | |
3806 | ((member token '("begin" "(" "@{")) | |
3807 | (if (smie-rule-hanging-p) (smie-rule-parent))) | |
3808 | ((equal token "if") | |
3809 | (and (not (smie-rule-bolp)) (smie-rule-prev-p "else") | |
3810 | (smie-rule-parent))))))) | |
3811 | @end example | |
3812 | ||
3813 | @noindent | |
3814 | A few things to note: | |
3815 | ||
3816 | @itemize | |
3817 | @item | |
3818 | The first case indicates the basic indentation increment to use. | |
3819 | If @code{sample-indent-basic} is nil, then SMIE uses the global | |
3820 | setting @code{smie-indent-basic}. The major mode could have set | |
3821 | @code{smie-indent-basic} buffer-locally instead, but that | |
3822 | is discouraged. | |
3823 | ||
3824 | @item | |
3825 | The two (identical) rules for the token @code{","} make SMIE try to be | |
3826 | more clever when the comma separator is placed at the beginning of | |
3827 | lines. It tries to outdent the separator so as to align the code after | |
3828 | the comma; for example: | |
3829 | ||
3830 | @example | |
3831 | x = longfunctionname ( | |
3832 | arg1 | |
3833 | , arg2 | |
3834 | ); | |
3835 | @end example | |
3836 | ||
3837 | @item | |
3838 | The rule for indentation after @code{":="} exists because otherwise | |
3839 | SMIE would treat @code{":="} as an infix operator and would align the | |
3840 | right argument with the left one. | |
3841 | ||
3842 | @item | |
3843 | The rule for indentation before @code{"begin"} is an example of the use | |
3844 | of virtual indentation: This rule is used only when @code{"begin"} is | |
3845 | hanging, which can happen only when @code{"begin"} is not at the | |
3846 | beginning of a line. So this is not used when indenting | |
3847 | @code{"begin"} itself but only when indenting something relative to this | |
3848 | @code{"begin"}. Concretely, this rule changes the indentation from: | |
3849 | ||
3850 | @example | |
3851 | if x > 0 then begin | |
3852 | dosomething(x); | |
3853 | end | |
3854 | @end example | |
3855 | to | |
3856 | @example | |
3857 | if x > 0 then begin | |
3858 | dosomething(x); | |
3859 | end | |
3860 | @end example | |
3861 | ||
3862 | @item | |
3863 | The rule for indentation before @code{"if"} is similar to the one for | |
3864 | @code{"begin"}, but where the purpose is to treat @code{"else if"} | |
3865 | as a single unit, so as to align a sequence of tests rather than indent | |
3866 | each test further to the right. This function does this only in the | |
3867 | case where the @code{"if"} is not placed on a separate line, hence the | |
3868 | @code{smie-rule-bolp} test. | |
3869 | ||
3870 | If we know that the @code{"else"} is always aligned with its @code{"if"} | |
3871 | and is always at the beginning of a line, we can use a more efficient | |
3872 | rule: | |
3873 | @example | |
3874 | ((equal token "if") | |
3875 | (and (not (smie-rule-bolp)) (smie-rule-prev-p "else") | |
3876 | (save-excursion | |
3877 | (sample-smie-backward-token) ;Jump before the "else". | |
3878 | (cons 'column (current-column))))) | |
3879 | @end example | |
3880 | ||
3881 | The advantage of this formulation is that it reuses the indentation of | |
3882 | the previous @code{"else"}, rather than going all the way back to the | |
3883 | first @code{"if"} of the sequence. | |
3884 | @end itemize | |
3885 | ||
b8d4c8d0 GM |
3886 | @node Desktop Save Mode |
3887 | @section Desktop Save Mode | |
3888 | @cindex desktop save mode | |
3889 | ||
3890 | @dfn{Desktop Save Mode} is a feature to save the state of Emacs from | |
3891 | one session to another. The user-level commands for using Desktop | |
3892 | Save Mode are described in the GNU Emacs Manual (@pxref{Saving Emacs | |
3893 | Sessions,,, emacs, the GNU Emacs Manual}). Modes whose buffers visit | |
3894 | a file, don't have to do anything to use this feature. | |
3895 | ||
3896 | For buffers not visiting a file to have their state saved, the major | |
3897 | mode must bind the buffer local variable @code{desktop-save-buffer} to | |
3898 | a non-@code{nil} value. | |
3899 | ||
3900 | @defvar desktop-save-buffer | |
3901 | If this buffer-local variable is non-@code{nil}, the buffer will have | |
3902 | its state saved in the desktop file at desktop save. If the value is | |
3903 | a function, it is called at desktop save with argument | |
3904 | @var{desktop-dirname}, and its value is saved in the desktop file along | |
3905 | with the state of the buffer for which it was called. When file names | |
3906 | are returned as part of the auxiliary information, they should be | |
3907 | formatted using the call | |
3908 | ||
3909 | @example | |
3910 | (desktop-file-name @var{file-name} @var{desktop-dirname}) | |
3911 | @end example | |
3912 | ||
3913 | @end defvar | |
3914 | ||
3915 | For buffers not visiting a file to be restored, the major mode must | |
3916 | define a function to do the job, and that function must be listed in | |
3917 | the alist @code{desktop-buffer-mode-handlers}. | |
3918 | ||
3919 | @defvar desktop-buffer-mode-handlers | |
3920 | Alist with elements | |
3921 | ||
3922 | @example | |
3923 | (@var{major-mode} . @var{restore-buffer-function}) | |
3924 | @end example | |
3925 | ||
3926 | The function @var{restore-buffer-function} will be called with | |
3927 | argument list | |
3928 | ||
3929 | @example | |
3930 | (@var{buffer-file-name} @var{buffer-name} @var{desktop-buffer-misc}) | |
3931 | @end example | |
3932 | ||
3933 | and it should return the restored buffer. | |
3934 | Here @var{desktop-buffer-misc} is the value returned by the function | |
3935 | optionally bound to @code{desktop-save-buffer}. | |
3936 | @end defvar | |
3937 | ||
3938 | @ignore | |
769741e3 SM |
3939 | Local Variables: |
3940 | fill-column: 72 | |
3941 | End: | |
b8d4c8d0 | 3942 | @end ignore |