the first line as well.
@cindex shell scripts, and local file variables
+@cindex man pages, and local file variables
In shell scripts, the first line is used to identify the script
interpreter, so you cannot put any local variables there. To
accommodate this, Emacs looks for local variable specifications in the
@emph{second} line when the first line specifies an interpreter.
+The same is true for man pages which start with the magic string
+@samp{'\"} to specify a list of troff preprocessors (not all do,
+however).
A @dfn{local variables list} goes near the end of the file, in the
last page. (It is often best to put it on a page by itself.) The local
Emacs installation directory, typically
@file{/usr/local/share/emacs/site-lisp}.
- If you have a large amount of code in your @file{.emacs} file, you
-should rename it to @file{~/.emacs.el}, and byte-compile it. @xref{Byte
-Compilation,, Byte Compilation, elisp, the Emacs Lisp Reference Manual},
-for more information about compiling Emacs Lisp programs.
+ Byte-compiling your @file{.emacs} is not recommended (@pxref{Byte
+Compilation,, Byte Compilation, elisp, the Emacs Lisp Reference
+Manual}). It generally does not speed up startup very much, and often
+leads to problems when you forget to recompile the file. A better
+solution is to use the Emacs server to reduce the number of times you
+have to start Emacs (@pxref{Emacs Server}). If your @file{.emacs}
+defines many functions, consider moving them to a separate
+(byte-compiled) file that you load in your @file{.emacs}.
If you are going to write actual Emacs Lisp programs that go beyond
minor customization, you should read the @cite{Emacs Lisp Reference Manual}.
The usual purpose of the terminal-specific library is to map the
escape sequences used by the terminal's function keys onto more
-meaningful names, using @code{function-key-map}. See the file
+meaningful names, using @code{input-decode-map} (or
+@code{function-key-map} before it). See the file
@file{term/lk201.el} for an example of how this is done. Many function
keys are mapped automatically according to the information in the
Termcap data base; the terminal-specific library needs to map only the