summaryrefslogtreecommitdiff
path: root/lispref/variables.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2003-06-30 10:43:01 +0000
committerRichard M. Stallman <rms@gnu.org>2003-06-30 10:43:01 +0000
commit6fe508678c84a0291bd95e0f726c14335a5dccff (patch)
tree3e7d18bda01cd49d0a55d1f4fee7438c151be60c /lispref/variables.texi
parent74eee906cca8f02e46d7399c35b1051344d7d2d5 (diff)
downloademacs-6fe508678c84a0291bd95e0f726c14335a5dccff.tar.gz
Minor Texinfo usage fix.
Diffstat (limited to 'lispref/variables.texi')
-rw-r--r--lispref/variables.texi14
1 files changed, 8 insertions, 6 deletions
diff --git a/lispref/variables.texi b/lispref/variables.texi
index 0b316af897c..268b8788500 100644
--- a/lispref/variables.texi
+++ b/lispref/variables.texi
@@ -576,11 +576,12 @@ this feature is largely obsoleted by @code{defcustom}
(@pxref{Customization}).
@strong{Warning:} If the @code{defconst} and @code{defvar} special
-forms are used while the variable has a local binding, they set the
-local binding's value; the global binding is not changed. This is not
-what you usually want. To prevent it, use these special forms at top
-level in a file, where normally no local binding is in effect, and make
-sure to load the file before making a local binding for the variable.
+forms are used while the variable has a local binding (made with
+@code{let}, or a function argument), they set the local-binding's
+value; the top-level binding is not changed. This is not what you
+usually want. To prevent it, use these special forms at top level in
+a file, where normally no local binding is in effect, and make sure to
+load the file before making a local binding for the variable.
@node Tips for Defining
@section Tips for Defining Variables Robustly
@@ -1749,7 +1750,8 @@ for one of these variables is ignored.
@end defvar
@defun risky-local-variable-p sym
-Returns non-nil if @var{sym} is risky for any of the reasons stated above.
+Returns non-@code{nil} if @var{sym} is risky for any of the reasons
+stated above.
@end defun
The @samp{Eval:} ``variable'' is also a potential loophole, so Emacs