summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorGlenn Morris <rgm@gnu.org>2007-09-05 03:21:57 +0000
committerGlenn Morris <rgm@gnu.org>2007-09-05 03:21:57 +0000
commitc7a6fd7f03caf963baa519e263350d1b9d912674 (patch)
tree0225f6a76b11efdadecc944d3bf8f0bea94bfe1b /man
parent72b1ff2fa95fd98ba88995e6fa6cb79ea988b363 (diff)
downloademacs-c7a6fd7f03caf963baa519e263350d1b9d912674.tar.gz
Improve wording of previous change.
Diffstat (limited to 'man')
-rw-r--r--man/custom.texi7
1 files changed, 3 insertions, 4 deletions
diff --git a/man/custom.texi b/man/custom.texi
index d40e426ae17..d496ab84b19 100644
--- a/man/custom.texi
+++ b/man/custom.texi
@@ -1229,10 +1229,9 @@ particularly @dfn{risky}: there is seldom any reason to specify them
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,
-@kbd{!} is an option at the prompt. If you enter @kbd{!} in this case,
-all the local variables are applied, but only the non-risky ones are
-marked as safe for the future. If you really want to
+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}).