aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2001-07-08 16:45:01 +0000
committerRichard M. Stallman2001-07-08 16:45:01 +0000
commitda6e9d86abb9abd281b732a750f8dbb164e06fb5 (patch)
tree5e3ea29c212fffdcfd73eb87f2258b59df380b43
parent24b97d4bf8cb03379c1b7e9ffe21a5ce3e657ba1 (diff)
downloademacs-da6e9d86abb9abd281b732a750f8dbb164e06fb5.tar.gz
emacs-da6e9d86abb9abd281b732a750f8dbb164e06fb5.zip
Explain more clearly what it takes to make a customization permanent.
Explain global vs local minor modes first thing, then list the modes.
-rw-r--r--man/custom.texi63
1 files changed, 32 insertions, 31 deletions
diff --git a/man/custom.texi b/man/custom.texi
index bd554b5d4e8..ddd51360177 100644
--- a/man/custom.texi
+++ b/man/custom.texi
@@ -10,14 +10,13 @@
10behavior of Emacs in minor ways. See @cite{The Emacs Lisp Reference 10behavior of Emacs in minor ways. See @cite{The Emacs Lisp Reference
11Manual} for how to make more far-reaching changes. 11Manual} for how to make more far-reaching changes.
12 12
13 All kinds of customization affect only the particular Emacs session 13 Customization that you do within Emacs normally affects only the
14that you do them in. They are completely lost when you kill the Emacs 14particular Emacs session that you do it in--it does not persist
15session, and have no effect on other Emacs sessions you may run at the 15between sessions unless you save the customization in a file such as
16same time or later. The only way an Emacs session can affect anything 16@file{.emacs} or @file{.Xdefaults} that will change future sessions.
17outside of it is by writing a file; in particular, the only way to make 17@xref{Init File}. In the customization buffer, if you use a
18a customization ``permanent'' is to put something in your @file{.emacs} 18command to save customizations for future sessions, this actually
19file or other appropriate file to do the customization in each session. 19works by editing @file{.emacs} for you.
20@xref{Init File}.
21 20
22@menu 21@menu
23* Minor Modes:: Each minor mode is one feature you can turn on 22* Minor Modes:: Each minor mode is one feature you can turn on
@@ -61,12 +60,31 @@ off and off if it was on. This is known as @dfn{toggling}. A positive
61argument always turns the mode on, and an explicit zero argument or a 60argument always turns the mode on, and an explicit zero argument or a
62negative argument always turns it off. 61negative argument always turns it off.
63 62
64 Enabling or disabling some minor modes applies only to the current 63 Some minor modes are global: while enabled, they affect everything
65buffer; each buffer is independent of the other buffers. Therefore, you 64you do in the Emacs session, in all buffers. Other minor modes are
66can enable the mode in particular buffers and disable it in others. The 65buffer-local; they apply only to the current buffer, so you can enable
67per-buffer minor modes include Abbrev mode, Auto Fill mode, Auto Save 66the mode in certain buffers and not others.
68mode, Font-Lock mode, ISO Accents mode, Outline minor 67
69mode, Overwrite mode, and Binary Overwrite mode. 68 For most minor modes, the command name is also the name of a
69variable which directly controls the mode. The mode is enabled
70whenever this variable's value is non-@code{nil}, and the minor-mode
71command works by setting the variable. For example, the command
72@code{outline-minor-mode} works by setting the value of
73@code{outline-minor-mode} as a variable; it is this variable that
74directly turns Outline minor mode on and off. To check whether a
75given minor mode works this way, use @kbd{C-h v} to ask for
76documentation on the variable name.
77
78 These minor-mode variables provide a good way for Lisp programs to turn
79minor modes on and off; they are also useful in a file's local variables
80list. But please think twice before setting minor modes with a local
81variables list, because most minor modes are matter of user
82preference---other users editing the same file might not want the same
83minor modes you prefer.
84
85 The buffer-local minor modes include Abbrev mode, Auto Fill mode,
86Auto Save mode, Font-Lock mode, ISO Accents mode, Outline minor mode,
87Overwrite mode, and Binary Overwrite mode.
70 88
71 Abbrev mode allows you to define abbreviations that automatically expand 89 Abbrev mode allows you to define abbreviations that automatically expand
72as you type them. For example, @samp{amd} might expand to @samp{abbrev 90as you type them. For example, @samp{amd} might expand to @samp{abbrev
@@ -149,23 +167,6 @@ explicitly ``reactivate'' it, before each command that uses the region.
149The advantage of Transient Mark mode is that Emacs can display the 167The advantage of Transient Mark mode is that Emacs can display the
150region highlighted (currently only when using X). @xref{Mark}. 168region highlighted (currently only when using X). @xref{Mark}.
151 169
152 For most minor modes, the command name is also the name of a variable
153which directly controls the mode. The mode is enabled whenever this
154variable's value is non-@code{nil}, and the minor-mode command works by
155setting the variable. For example, the command
156@code{outline-minor-mode} works by setting the value of
157@code{outline-minor-mode} as a variable; it is this variable that
158directly turns Outline minor mode on and off. To check whether a given
159minor mode works this way, use @kbd{C-h v} to ask for documentation on
160the variable name.
161
162 These minor-mode variables provide a good way for Lisp programs to turn
163minor modes on and off; they are also useful in a file's local variables
164list. But please think twice before setting minor modes with a local
165variables list, because most minor modes are matter of user
166preference---other users editing the same file might not want the same
167minor modes you prefer.
168
169@node Variables 170@node Variables
170@section Variables 171@section Variables
171@cindex variable 172@cindex variable