summaryrefslogtreecommitdiff
path: root/lispref/variables.texi
diff options
context:
space:
mode:
authorChong Yidong <cyd@stupidchicken.com>2006-02-14 15:17:27 +0000
committerChong Yidong <cyd@stupidchicken.com>2006-02-14 15:17:27 +0000
commit764d6d17d36f16dec1ea4b5091f19815ef2d5603 (patch)
treefae72638e74dbb2a62cb9835ec190d090a084e2c /lispref/variables.texi
parent542f7c55b40c5c020777b283c22702c88c5080d6 (diff)
downloademacs-764d6d17d36f16dec1ea4b5091f19815ef2d5603.tar.gz
Typo.
Diffstat (limited to 'lispref/variables.texi')
-rw-r--r--lispref/variables.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/lispref/variables.texi b/lispref/variables.texi
index d272e78d3a5..2677dd72bdb 100644
--- a/lispref/variables.texi
+++ b/lispref/variables.texi
@@ -1784,7 +1784,7 @@ file variables specified in that file. A variable can be marked as
@dfn{safe} by setting its @code{safe-local-variable} property. If the
property is @code{t}, that variable is always considered safe,
regardless of the value assigned to it. The
-@code{safe-local-variable} property can also be a a function taking
+@code{safe-local-variable} property can also be a function taking
exactly one argument. In that case, Emacs considers it safe to give
the variable a certain value if the function returns non-@code{nil}
when called with that value as argument. Many commonly-encountered