1 @c This is part of the Emacs manual.
2 @c Copyright (C) 1985-1987, 1993-1995, 1997, 2000-2015 Free Software
4 @c See file emacs.texi for copying conditions.
6 @chapter Major and Minor Modes
8 Emacs contains many @dfn{editing modes} that alter its basic
9 behavior in useful ways. These are divided into @dfn{major modes} and
12 Major modes provide specialized facilities for working on a
13 particular file type, such as a C source file (@pxref{Programs}), or a
14 particular type of non-file buffer, such as a shell buffer
15 (@pxref{Shell}). Major modes are mutually exclusive; each buffer has
16 one and only one major mode at any time.
18 Minor modes are optional features which you can turn on or off, not
19 necessarily specific to a type of file or buffer. For example, Auto
20 Fill mode is a minor mode in which @key{SPC} breaks lines between
21 words as you type (@pxref{Auto Fill}). Minor modes are independent of
22 one another, and of the selected major mode.
25 * Major Modes:: Text mode vs. Lisp mode vs. C mode...
26 * Minor Modes:: Each minor mode is a feature you can turn on
27 independently of any others.
28 * Choosing Modes:: How modes are chosen when visiting files.
35 @kindex TAB @r{(and major modes)}
36 @kindex DEL @r{(and major modes)}
37 @kindex C-j @r{(and major modes)}
39 Every buffer possesses a major mode, which determines the editing
40 behavior of Emacs while that buffer is current. The mode line
41 normally shows the name of the current major mode, in parentheses
44 The least specialized major mode is called @dfn{Fundamental mode}.
45 This mode has no mode-specific redefinitions or variable settings, so
46 that each Emacs command behaves in its most general manner, and each
47 user option variable is in its default state.
49 For editing text of a specific type that Emacs knows about, such as
50 Lisp code or English text, you typically use a more specialized major
51 mode, such as Lisp mode or Text mode. Most major modes fall into
52 three major groups. The first group contains modes for normal text,
53 either plain or with mark-up. It includes Text mode, HTML mode, SGML
54 mode, @TeX{} mode and Outline mode. The second group contains modes
55 for specific programming languages. These include Lisp mode (which
56 has several variants), C mode, Fortran mode, and others. The third
57 group consists of major modes that are not associated directly with
58 files; they are used in buffers created for specific purposes by
59 Emacs, such as Dired mode for buffers made by Dired (@pxref{Dired}),
60 Message mode for buffers made by @kbd{C-x m} (@pxref{Sending Mail}),
61 and Shell mode for buffers used to communicate with an inferior shell
62 process (@pxref{Interactive Shell}).
64 Usually, the major mode is automatically set by Emacs, when you
65 first visit a file or create a buffer (@pxref{Choosing Modes}). You
66 can explicitly select a new major mode by using an @kbd{M-x} command.
67 Take the name of the mode and add @code{-mode} to get the name of the
68 command to select that mode (e.g., @kbd{M-x lisp-mode} enters Lisp mode).
71 The value of the buffer-local variable @code{major-mode} is a symbol
72 with the same name as the major mode command (e.g., @code{lisp-mode}).
73 This variable is set automatically; you should not change it yourself.
75 The default value of @code{major-mode} determines the major mode to
76 use for files that do not specify a major mode, and for new buffers
77 created with @kbd{C-x b}. Normally, this default value is the symbol
78 @code{fundamental-mode}, which specifies Fundamental mode. You can
79 change this default value via the Customization interface (@pxref{Easy
80 Customization}), or by adding a line like this to your init file
84 (setq-default major-mode 'text-mode)
88 If the default value of @code{major-mode} is @code{nil}, the major
89 mode is taken from the previously current buffer.
91 Specialized major modes often change the meanings of certain keys to
92 do something more suitable for the mode. For instance, programming
93 language modes bind @key{TAB} to indent the current line according to
94 the rules of the language (@pxref{Indentation}). The keys that are
95 commonly changed are @key{TAB}, @key{DEL}, and @kbd{C-j}. Many modes
96 also define special commands of their own, usually bound in the prefix
97 key @kbd{C-c}. Major modes can also alter user options and variables;
98 for instance, programming language modes typically set a buffer-local
99 value for the variable @code{comment-start}, which determines how
100 source code comments are delimited (@pxref{Comments}).
102 @findex describe-mode
104 To view the documentation for the current major mode, including a
105 list of its key bindings, type @code{C-h m} (@code{describe-mode}).
108 @vindex text-mode-hook
109 @vindex prog-mode-hook
110 Every major mode, apart from Fundamental mode, defines a @dfn{mode
111 hook}, a customizable list of Lisp functions to run each time the mode
112 is enabled in a buffer. @xref{Hooks}, for more information about
113 hooks. Each mode hook is named after its major mode, e.g., Fortran
114 mode has @code{fortran-mode-hook}. Furthermore, all text-based major
115 modes run @code{text-mode-hook}, and all programming language modes
116 run @code{prog-mode-hook}, prior to running their own mode hooks.
117 Hook functions can look at the value of the variable @code{major-mode}
118 to see which mode is actually being entered.
120 Mode hooks are commonly used to enable minor modes (@pxref{Minor
121 Modes}). For example, you can put the following lines in your init
122 file to enable Flyspell minor mode in all text-based major modes
123 (@pxref{Spelling}), and Eldoc minor mode in Emacs Lisp mode
127 (add-hook 'text-mode-hook 'flyspell-mode)
128 (add-hook 'emacs-lisp-mode-hook 'eldoc-mode)
136 A minor mode is an optional editing mode that alters the behavior of
137 Emacs in some well-defined way. Unlike major modes, any number of
138 minor modes can be in effect at any time. Some minor modes are
139 @dfn{buffer-local}, and can be turned on (enabled) in certain buffers
140 and off (disabled) in others. Other minor modes are @dfn{global}:
141 while enabled, they affect everything you do in the Emacs session, in
142 all buffers. Most minor modes are disabled by default, but a few are
145 Most buffer-local minor modes say in the mode line when they are
146 enabled, just after the major mode indicator. For example,
147 @samp{Fill} in the mode line means that Auto Fill mode is enabled.
150 @cindex mode commands for minor modes
151 Like major modes, each minor mode is associated with a @dfn{mode
152 command}, whose name consists of the mode name followed by
153 @samp{-mode}. For instance, the mode command for Auto Fill mode is
154 @code{auto-fill-mode}. But unlike a major mode command, which simply
155 enables the mode, the mode command for a minor mode can either enable
160 If you invoke the mode command directly with no prefix argument
161 (either via @kbd{M-x}, or by binding it to a key and typing that key;
162 @pxref{Key Bindings}), that @dfn{toggles} the minor mode. The minor
163 mode is turned on if it was off, and turned off if it was on.
166 If you invoke the mode command with a prefix argument, the minor mode
167 is unconditionally turned off if that argument is zero or negative;
168 otherwise, it is unconditionally turned on.
171 If the mode command is called via Lisp, the minor mode is
172 unconditionally turned on if the argument is omitted or @code{nil}.
173 This makes it easy to turn on a minor mode from a major mode's mode
174 hook (@pxref{Major Modes}). A non-@code{nil} argument is handled like
175 an interactive prefix argument, as described above.
178 Most minor modes also have a @dfn{mode variable}, with the same name
179 as the mode command. Its value is non-@code{nil} if the mode is
180 enabled, and @code{nil} if it is disabled. In general, you should not
181 try to enable or disable the mode by changing the value of the mode
182 variable directly in Lisp; you should run the mode command instead.
183 However, setting the mode variable through the Customize interface
184 (@pxref{Easy Customization}) will always properly enable or disable
185 the mode, since Customize automatically runs the mode command for you.
187 The following is a list of some buffer-local minor modes:
191 Abbrev mode automatically expands text based on pre-defined
192 abbreviation definitions. @xref{Abbrevs}.
195 Auto Fill mode inserts newlines as you type to prevent lines from
196 becoming too long. @xref{Filling}.
199 Auto Save mode saves the buffer contents periodically to reduce the
200 amount of work you can lose in case of a crash. @xref{Auto Save}.
203 Electric Quote mode automatically converts quotation marks. For
204 example, it requotes text typed @t{`like this'} to text @t{‘like
205 this’}. You can control what kind of text it operates in, and you can
206 disable it entirely in individual buffers. @xref{Quotation Marks}.
209 Enriched mode enables editing and saving of formatted text.
210 @xref{Enriched Text}.
213 Flyspell mode automatically highlights misspelled words.
217 Font-Lock mode automatically highlights certain textual units found in
218 programs. It is enabled globally by default, but you can disable it
219 in individual buffers. @xref{Faces}.
224 Linum mode displays each line's line number in the window's left margin.
227 Outline minor mode provides similar facilities to the major mode
228 called Outline mode. @xref{Outline Mode}.
230 @cindex Overwrite mode
231 @cindex mode, Overwrite
232 @findex overwrite-mode
235 Overwrite mode causes ordinary printing characters to replace existing
236 text instead of shoving it to the right. For example, if point is in
237 front of the @samp{B} in @samp{FOOBAR}, then in Overwrite mode typing
238 a @kbd{G} changes it to @samp{FOOGAR}, instead of producing
239 @samp{FOOGBAR} as usual. In Overwrite mode, the command @kbd{C-q}
240 inserts the next character whatever it may be, even if it is a
241 digit---this gives you a way to insert a character instead of
242 replacing an existing character. The mode command,
243 @code{overwrite-mode}, is bound to the @key{Insert} key.
245 @findex binary-overwrite-mode
247 Binary Overwrite mode is a variant of Overwrite mode for editing
248 binary files; it treats newlines and tabs like other characters, so
249 that they overwrite other characters and can be overwritten by them.
250 In Binary Overwrite mode, digits after @kbd{C-q} specify an octal
251 character code, as usual.
254 Visual Line mode performs ``word wrapping'', causing long lines to be
255 wrapped at word boundaries. @xref{Visual Line Mode}.
259 And here are some useful global minor modes:
263 Column Number mode enables display of the current column number in the
264 mode line. @xref{Mode Line}.
267 Delete Selection mode causes text insertion to first delete the text
268 in the region, if the region is active. @xref{Using Region}.
271 Icomplete mode displays an indication of available completions when
272 you are in the minibuffer and completion is active. @xref{Icomplete}.
275 Line Number mode enables display of the current line number in the
276 mode line. It is enabled by default. @xref{Mode Line}.
279 Menu Bar mode gives each frame a menu bar. It is enabled by default.
283 Scroll Bar mode gives each window a scroll bar. It is enabled by
284 default, but the scroll bar is only displayed on graphical terminals.
288 Tool Bar mode gives each frame a tool bar. It is enabled by default,
289 but the tool bar is only displayed on graphical terminals. @xref{Tool
293 Transient Mark mode highlights the region, and makes many Emacs
294 commands operate on the region when the mark is active. It is enabled
295 by default. @xref{Mark}.
299 @section Choosing File Modes
301 @cindex choosing a major mode
302 @cindex choosing a minor mode
303 @vindex auto-mode-alist
304 When you visit a file, Emacs chooses a major mode automatically.
305 Normally, it makes the choice based on the file name---for example,
306 files whose names end in @samp{.c} are normally edited in C mode---but
307 sometimes it chooses the major mode based on special text in the file.
308 This special text can also be used to enable buffer-local minor modes.
310 Here is the exact procedure:
312 First, Emacs checks whether the file contains file-local mode
313 variables. @xref{File Variables}. If there is a file-local variable
314 that specifies a major mode, then Emacs uses that major mode, ignoring
315 all other criteria. There are several methods to specify a major mode
316 using a file-local variable; the simplest is to put the mode name in
317 the first nonblank line, preceded and followed by @samp{-*-}. Other
318 text may appear on the line as well. For example,
325 tells Emacs to use Lisp mode. Note how the semicolon is used to make
326 Lisp treat this line as a comment. You could equivalently write
333 You can also use file-local variables to specify buffer-local minor
334 modes, by using @code{eval} specifications. For example, this first
335 nonblank line puts the buffer in Lisp mode and enables Auto-Fill mode:
338 ; -*- mode: Lisp; eval: (auto-fill-mode 1); -*-
342 Note, however, that it is usually inappropriate to enable minor modes
343 this way, since most minor modes represent individual user
344 preferences. If you personally want to use a minor mode for a
345 particular file type, it is better to enable the minor mode via a
346 major mode hook (@pxref{Major Modes}).
348 @vindex interpreter-mode-alist
349 Second, if there is no file variable specifying a major mode, Emacs
350 checks whether the file's contents begin with @samp{#!}. If so, that
351 indicates that the file can serve as an executable shell command,
352 which works by running an interpreter named on the file's first line
353 (the rest of the file is used as input to the interpreter).
354 Therefore, Emacs tries to use the interpreter name to choose a mode.
355 For instance, a file that begins with @samp{#!/usr/bin/perl} is opened
356 in Perl mode. The variable @code{interpreter-mode-alist} specifies
357 the correspondence between interpreter program names and major modes.
359 When the first line starts with @samp{#!}, you usually cannot use
360 the @samp{-*-} feature on the first line, because the system would get
361 confused when running the interpreter. So Emacs looks for @samp{-*-}
362 on the second line in such files as well as on the first line. The
363 same is true for man pages which start with the magic string
364 @samp{'\"} to specify a list of troff preprocessors.
366 @vindex magic-mode-alist
367 Third, Emacs tries to determine the major mode by looking at the
368 text at the start of the buffer, based on the variable
369 @code{magic-mode-alist}. By default, this variable is @code{nil} (an
370 empty list), so Emacs skips this step; however, you can customize it
371 in your init file (@pxref{Init File}). The value should be a list of
375 (@var{regexp} . @var{mode-function})
379 where @var{regexp} is a regular expression (@pxref{Regexps}), and
380 @var{mode-function} is a major mode command. If the text at the
381 beginning of the file matches @var{regexp}, Emacs chooses the major
382 mode specified by @var{mode-function}.
384 Alternatively, an element of @code{magic-mode-alist} may have the form
387 (@var{match-function} . @var{mode-function})
391 where @var{match-function} is a Lisp function that is called at the
392 beginning of the buffer; if the function returns non-@code{nil}, Emacs
393 set the major mode with @var{mode-function}.
395 Fourth---if Emacs still hasn't found a suitable major mode---it
396 looks at the file's name. The correspondence between file names and
397 major modes is controlled by the variable @code{auto-mode-alist}. Its
398 value is a list in which each element has this form,
401 (@var{regexp} . @var{mode-function})
408 (@var{regexp} @var{mode-function} @var{flag})
412 For example, one element normally found in the list has the form
413 @code{(@t{"\\.c\\'"} . c-mode)}, and it is responsible for selecting C
414 mode for files whose names end in @file{.c}. (Note that @samp{\\} is
415 needed in Lisp syntax to include a @samp{\} in the string, which must
416 be used to suppress the special meaning of @samp{.} in regexps.) If
417 the element has the form @code{(@var{regexp} @var{mode-function}
418 @var{flag})} and @var{flag} is non-@code{nil}, then after calling
419 @var{mode-function}, Emacs discards the suffix that matched
420 @var{regexp} and searches the list again for another match.
422 @vindex auto-mode-case-fold
423 On GNU/Linux and other systems with case-sensitive file names, Emacs
424 performs a case-sensitive search through @code{auto-mode-alist}; if
425 this search fails, it performs a second case-insensitive search
426 through the alist. To suppress the second search, change the variable
427 @code{auto-mode-case-fold} to @code{nil}. On systems with
428 case-insensitive file names, such as Microsoft Windows, Emacs performs
429 a single case-insensitive search through @code{auto-mode-alist}.
431 @vindex magic-fallback-mode-alist
432 Finally, if Emacs @emph{still} hasn't found a major mode to use, it
433 compares the text at the start of the buffer to the variable
434 @code{magic-fallback-mode-alist}. This variable works like
435 @code{magic-mode-alist}, described above, except that is consulted
436 only after @code{auto-mode-alist}. By default,
437 @code{magic-fallback-mode-alist} contains forms that check for image
438 files, HTML/XML/SGML files, and PostScript files.
441 If you have changed the major mode of a buffer, you can return to
442 the major mode Emacs would have chosen automatically, by typing
443 @kbd{M-x normal-mode}. This is the same function that
444 @code{find-file} calls to choose the major mode. It also processes
445 the file's @samp{-*-} line or local variables list (if any).
446 @xref{File Variables}.
448 @vindex change-major-mode-with-file-name
449 The commands @kbd{C-x C-w} and @code{set-visited-file-name} change to
450 a new major mode if the new file name implies a mode (@pxref{Saving}).
451 (@kbd{C-x C-s} does this too, if the buffer wasn't visiting a file.)
452 However, this does not happen if the buffer contents specify a major
453 mode, and certain ``special'' major modes do not allow the mode to
454 change. You can turn off this mode-changing feature by setting
455 @code{change-major-mode-with-file-name} to @code{nil}.