* lispref/variables.texi (File Local Variables): Don't recommend quoting!

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index d2e86c25cc17ed45ed0f299fc66d0ff3f7934f44..d27f58c0efa45d2b64a697a0eaacf14109bb1f61 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2013-08-26  Stefan Monnier  <monnier@iro.umontreal.ca>
+
+       * variables.texi (File Local Variables): Don't recommend quoting!  Ever!
+
 2013-08-20  Eli Zaretskii  <eliz@gnu.org>
 
        * files.texi (Information about Files): Mention file names with

diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi
index 557add738ba3beed19d605ed672950b7f895f8a8..866f3774999e545dbf9da0025981f375a7374186 100644 (file)
--- a/doc/lispref/variables.texi
+++ b/doc/lispref/variables.texi
@@ -1649,8 +1649,7 @@ non-@code{nil} given that value.  Many commonly-encountered file
 variables have @code{safe-local-variable} properties; these include
 @code{fill-column}, @code{fill-prefix}, and @code{indent-tabs-mode}.
 For boolean-valued variables that are safe, use @code{booleanp} as the
-property value.  Lambda expressions should be quoted so that
-@code{describe-variable} can display the predicate.
+property value.
 
   When defining a user option using @code{defcustom}, you can set its
 @code{safe-local-variable} property by adding the arguments