aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/emacs/package.texi10
-rw-r--r--doc/lispref/variables.texi14
2 files changed, 14 insertions, 10 deletions
diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi
index 3c099838059..5662c857de9 100644
--- a/doc/emacs/package.texi
+++ b/doc/emacs/package.texi
@@ -238,10 +238,12 @@ controlled by the value of @code{package-menu-hide-low-priority}.)
238 238
239 Once a package is downloaded and installed, it is @dfn{loaded} into 239 Once a package is downloaded and installed, it is @dfn{loaded} into
240the current Emacs session. Loading a package is not quite the same as 240the current Emacs session. Loading a package is not quite the same as
241loading a Lisp library (@pxref{Lisp Libraries}); its effect varies 241loading a Lisp library (@pxref{Lisp Libraries}); loading a package
242from package to package. Most packages just make some new commands 242adds its directory to @code{load-path} and loads its autoloads. The
243available, while others have more wide-ranging effects on the Emacs 243effect of a package's autoloads varies from package to package. Most
244session. For such information, consult the package's help buffer. 244packages just make some new commands available, while others have more
245wide-ranging effects on the Emacs session. For such information,
246consult the package's help buffer.
245 247
246 By default, Emacs also automatically loads all installed packages in 248 By default, Emacs also automatically loads all installed packages in
247subsequent Emacs sessions. This happens at startup, after processing 249subsequent Emacs sessions. This happens at startup, after processing
diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi
index dd3f18be4e1..418a4161a7a 100644
--- a/doc/lispref/variables.texi
+++ b/doc/lispref/variables.texi
@@ -974,7 +974,7 @@ itself.
974 974
975@cindex lexical environment 975@cindex lexical environment
976 Here is how lexical binding works. Each binding construct defines a 976 Here is how lexical binding works. Each binding construct defines a
977@dfn{lexical environment}, specifying the symbols that are bound 977@dfn{lexical environment}, specifying the variables that are bound
978within the construct and their local values. When the Lisp evaluator 978within the construct and their local values. When the Lisp evaluator
979wants the current value of a variable, it looks first in the lexical 979wants the current value of a variable, it looks first in the lexical
980environment; if the variable is not specified in there, it looks in 980environment; if the variable is not specified in there, it looks in
@@ -1032,11 +1032,13 @@ lives on even after the @code{let} binding construct has exited. Each
1032time we evaluate the closure, it increments @code{x}, using the 1032time we evaluate the closure, it increments @code{x}, using the
1033binding of @code{x} in that lexical environment. 1033binding of @code{x} in that lexical environment.
1034 1034
1035 Note that functions like @code{symbol-value}, @code{boundp}, and 1035 Note that unlike dynamic variables which are tied to the symbol
1036@code{set} only retrieve or modify a variable's dynamic binding 1036object itself, the relationship between lexical variables and symbols
1037(i.e., the contents of its symbol's value cell). Also, the code in 1037is only present in the interpreter (or compiler). Therefore,
1038the body of a @code{defun} or @code{defmacro} cannot refer to 1038functions which take a symbol argument (like @code{symbol-value},
1039surrounding lexical variables. 1039@code{boundp}, and @code{set}) can only retrieve or modify a
1040variable's dynamic binding (i.e., the contents of its symbol's value
1041cell).
1040 1042
1041@node Using Lexical Binding 1043@node Using Lexical Binding
1042@subsection Using Lexical Binding 1044@subsection Using Lexical Binding