From: Glenn Morris Date: Wed, 5 Sep 2007 03:22:50 +0000 (+0000) Subject: (Safe File Variables): Clarify `!' and risky variables. X-Git-Tag: emacs-pretest-23.0.90~11107 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=d61af56253764403d7c4ce8dd9a41cd378b2fd16;p=emacs.git (Safe File Variables): Clarify `!' and risky variables. --- diff --git a/man/ChangeLog b/man/ChangeLog index 8e58d905937..3cc76452fb3 100644 --- a/man/ChangeLog +++ b/man/ChangeLog @@ -1,3 +1,7 @@ +2007-09-05 Glenn Morris + + * custom.texi (Safe File Variables): Clarify `!' and risky variables. + 2007-09-01 Jay Belanger * calc.texi (Date Conversions): Clarify definition of diff --git a/man/custom.texi b/man/custom.texi index 3ab3ff0f636..d496ab84b19 100644 --- a/man/custom.texi +++ b/man/custom.texi @@ -1226,10 +1226,13 @@ safe. @cindex risky variable Some variables, such as @code{load-path}, are considered particularly @dfn{risky}: there is seldom any reason to specify them -as local variables, and changing them can be dangerous. Even if you -enter @kbd{!} at the confirmation prompt, Emacs will not record any -values as safe for these variables. If you really want to record safe -values for these variables, do it directly by customizing +as local variables, and changing them can be dangerous. If a file +contains only risky local variables, Emacs neither offers nor accepts +@kbd{!} as input at the confirmation prompt. If some of the local +variables in a file are risky, and some are only potentially unsafe, you +can enter @kbd{!} at the prompt. It applies all the variables, but only +marks the non-risky ones as safe for the future. If you really want to +record safe values for risky variables, do it directly by customizing @samp{safe-local-variable-values} (@pxref{Easy Customization}). @vindex enable-local-variables