From: Chong Yidong Date: Wed, 15 Feb 2006 01:37:53 +0000 (+0000) Subject: * custom.texi (Unsafe File Variables): File variable confirmation X-Git-Tag: emacs-pretest-22.0.90~4117 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=252293378b1467cd6dda2e69154fed991e6a6e8a;p=emacs.git * custom.texi (Unsafe File Variables): File variable confirmation assumed denied in batch mode. --- diff --git a/man/ChangeLog b/man/ChangeLog index f142ed75616..141115ec00e 100644 --- a/man/ChangeLog +++ b/man/ChangeLog @@ -1,3 +1,8 @@ +2006-02-14 Chong Yidong + + * custom.texi (Unsafe File Variables): File variable confirmation + assumed denied in batch mode. + 2006-02-14 Richard M. Stallman * building.texi (GDB User Interface Layout): Don't say `inferior' diff --git a/man/custom.texi b/man/custom.texi index 5b6dcde70ee..8c414e6393c 100644 --- a/man/custom.texi +++ b/man/custom.texi @@ -1194,6 +1194,9 @@ that file, and asks you for confirmation before setting them. You can type @samp{y} or @samp{SPC} to apply the local variables list, or @samp{n} to ignore it. + When Emacs is run in batch mode (@pxref{Initial Options}), it +assumes that the answer is @samp{n}. + There is a set of file variables and values that are known to be safe. For instance, it is safe to give @code{comment-column} or @code{fill-column} any integer value. If a file specifies only safe