summaryrefslogtreecommitdiff
path: root/doc/lispref/eval.texi
diff options
context:
space:
mode:
authorChong Yidong <cyd@gnu.org>2013-12-27 11:38:26 +0800
committerChong Yidong <cyd@gnu.org>2013-12-27 11:38:26 +0800
commit0f1d29342f29e666bb6abe4073a30b425a63d26c (patch)
treeea14e45e38b0618be18ba70606e5e68c93c3c6af /doc/lispref/eval.texi
parent9cab7521b388464b6028dbd27751019ff2afcdba (diff)
downloademacs-0f1d29342f29e666bb6abe4073a30b425a63d26c.tar.gz
More doc updates
* commands.texi (Reading One Event): Mention keyboard coding. * functions.texi (Function Cells): * eval.texi (Function Indirection): Update for the fact that symbol-function no longer signals an error. * keymaps.texi (Translation Keymaps, Translation Keymaps): * nonascii.texi (Terminal I/O Encoding): Copyedits. * data.c (Fsymbol_function): Doc fix.
Diffstat (limited to 'doc/lispref/eval.texi')
-rw-r--r--doc/lispref/eval.texi18
1 files changed, 8 insertions, 10 deletions
diff --git a/doc/lispref/eval.texi b/doc/lispref/eval.texi
index 4a63ec2add1..a321bfce6f7 100644
--- a/doc/lispref/eval.texi
+++ b/doc/lispref/eval.texi
@@ -242,11 +242,9 @@ it obtains a non-symbol. @xref{Function Names}, for more information
about symbol function indirection.
One possible consequence of this process is an infinite loop, in the
-event that a symbol's function cell refers to the same symbol. Or a
-symbol may have a void function cell, in which case the subroutine
-@code{symbol-function} signals a @code{void-function} error. But if
-neither of these things happens, we eventually obtain a non-symbol,
-which ought to be a function or other suitable object.
+event that a symbol's function cell refers to the same symbol.
+Otherwise, we eventually obtain a non-symbol, which ought to be a
+function or other suitable object.
@kindex invalid-function
More precisely, we should now have a Lisp function (a lambda
@@ -255,12 +253,12 @@ a special form, or an autoload object. Each of these types is a case
described in one of the following sections. If the object is not one
of these types, Emacs signals an @code{invalid-function} error.
- The following example illustrates the symbol indirection process. We
-use @code{fset} to set the function cell of a symbol and
+ The following example illustrates the symbol indirection process.
+We use @code{fset} to set the function cell of a symbol and
@code{symbol-function} to get the function cell contents
-(@pxref{Function Cells}). Specifically, we store the symbol @code{car}
-into the function cell of @code{first}, and the symbol @code{first} into
-the function cell of @code{erste}.
+(@pxref{Function Cells}). Specifically, we store the symbol
+@code{car} into the function cell of @code{first}, and the symbol
+@code{first} into the function cell of @code{erste}.
@example
@group