own contents are not included.
@findex customize-apropos
- To control more precisely what to customize, you can use @kbd{M-x
-customize-apropos}. You specify a regular expression as argument;
-then all @emph{loaded} settings and groups whose names match this
-regular expression are set up in the customization buffer. If you
-specify an empty regular expression, this includes @emph{all} loaded
-groups and settings---which takes a long time to set up.
+ For a more general way of controlling what to customize, you can use
+@kbd{M-x customize-apropos}. You specify a regular expression as
+argument; then all @emph{loaded} settings and groups whose names match
+this regular expression are set up in the customization buffer. If
+you specify an empty regular expression, this includes @emph{all}
+loaded groups and settings---which takes a long time to set up.
@findex customize-changed
When you upgrade to a new Emacs version, you might want to consider
Here is an example of a local variables list:
@example
-;;; Local Variables: ***
-;;; mode:lisp ***
-;;; comment-column:0 ***
-;;; comment-start: ";;; " ***
-;;; comment-end:"***" ***
-;;; End: ***
+;; Local Variables: **
+;; mode:lisp **
+;; comment-column:0 **
+;; comment-start: ";; " **
+;; comment-end:"**" **
+;; End: **
@end example
- Each line starts with the prefix @samp{;;; } and each line ends with
-the suffix @samp{ ***}. Emacs recognizes these as the prefix and
+ Each line starts with the prefix @samp{;; } and each line ends with
+the suffix @samp{ **}. Emacs recognizes these as the prefix and
suffix based on the first line of the list, by finding them
surrounding the magic string @samp{Local Variables:}; then it
automatically discards them from the other lines of the list.
The usual reason for using a prefix and/or suffix is to embed the
local variables list in a comment, so it won't confuse other programs
that the file is intended as input for. The example above is for a
-language where comment lines start with @samp{;;; } and end with
-@samp{***}; the local values for @code{comment-start} and
+language where comment lines start with @samp{;; } and end with
+@samp{**}; the local values for @code{comment-start} and
@code{comment-end} customize the rest of Emacs for this unusual
syntax. Don't use a prefix (or a suffix) if you don't need one.
You can type @kbd{y} or @key{SPC} to put the local variables list into
effect, or @kbd{n} to ignore it. When Emacs is run in batch mode
(@pxref{Initial Options}), it can't really ask you, so it assumes the
-answer @samp{n}.
+answer @kbd{n}.
Emacs normally recognizes certain variables/value pairs as safe.
For instance, it is safe to give @code{comment-column} or
@code{minibuffer-local-must-match-map} is for strict completion and
for cautious completion.
@item
-@code{minibuffer-local-filename-completion-map} and
+Finally, @code{minibuffer-local-filename-completion-map} and
@code{minibuffer-local-must-match-filename-map} are like the two
previous ones, but they are specifically for file name completion.
They do not bind @key{SPC}.
@cindex rebinding keys, permanently
@cindex startup (init file)
- When Emacs is started, it normally loads a Lisp program from the
-file @file{.emacs} or @file{.emacs.el} in your home directory
-(see @ref{General Variables, HOME}, if you don't know where that is).
+ When Emacs is started, it normally loads a Lisp program from the file
+@file{.emacs} or @file{.emacs.el} in your home directory (@pxref{Find Init}).
We call this file your @dfn{init file} because it specifies how to
initialize Emacs for you. You can use the command line switch
@samp{-q} to prevent loading your init file, and @samp{-u} (or