From: Eli Zaretskii <eliz@gnu.org>
Date: Sat, 2 Dec 2000 15:26:21 +0000 (+0000)
Subject: Docment that `eval' can be used with local variables in the first
X-Git-Tag: emacs-pretest-21.0.93~291
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=07eab3c32c8902f1f206946488af7b84d2e9243a;p=emacs.git

Docment that `eval' can be used with local variables in the first
line.  Tell that in shell scripts the second line is used for
local variables.
---

diff --git a/man/custom.texi b/man/custom.texi
index a09a18c6847..a8775bc0a9a 100644
--- a/man/custom.texi
+++ b/man/custom.texi
@@ -888,6 +888,15 @@ specify a value for the ``variable'' named @code{coding}.  The ``value''
 must be a coding system name that Emacs recognizes.  @xref{Coding
 Systems}.
 
+  The @code{eval} pseudo-variable, described below, can be specified in
+the first line as well.
+
+@cindex shell scripts, 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 accomodate
+for this, when Emacs visits a shell script, it looks for local variable
+specifications in the @emph{second} line.
+
   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
 variables list starts with a line containing the string @samp{Local