Fix the Lisp reference manual for older Texinfo
* doc/lispref/symbols.texi (Standard Properties): Don't provide empty reference. * doc/lispref/variables.texi (Lexical Binding): Don't abuse xref in a standalone sentence.
This commit is contained in:
parent
863fd1c276
commit
37b5b3ea91
2 changed files with 7 additions and 7 deletions
|
@ -560,12 +560,12 @@ symbol.
|
|||
|
||||
In some cases, the definition cannot be found by looking for the
|
||||
definition of another symbol. For example, a test file might use a
|
||||
macro to generate calls to @code{ert-deftest}
|
||||
(@pxref{,,,ert, ERT: Emacs Lisp Regression Testing}) where the code
|
||||
is boiler plate and only varying data need to be passed in.
|
||||
In such cases, the @code{find-function-type-alist} property of the
|
||||
symbol can be an alist that augments @code{find-function-regexp-alist}
|
||||
telling how to find the definition of symbols of this type.
|
||||
macro to generate calls to @code{ert-deftest} (@pxref{How to Write
|
||||
Tests,,,ert, ERT: Emacs Lisp Regression Testing}) where the code is
|
||||
boiler plate and only varying data need to be passed in. In such cases,
|
||||
the @code{find-function-type-alist} property of the symbol can be an
|
||||
alist that augments @code{find-function-regexp-alist} telling how to
|
||||
find the definition of symbols of this type.
|
||||
|
||||
In the example of a macro defining calls to @code{ert-deftest},
|
||||
the macro could put the property @code{find-function-type-alist} on each
|
||||
|
|
|
@ -1117,7 +1117,7 @@ cell).
|
|||
will use dynamic binding, even for new bindings such as a @code{let}
|
||||
binding. Depending on how the variable is declared, it can be
|
||||
special globally, for a single file, or for a portion of a file.
|
||||
@xref{Dynamic Binding} for details.
|
||||
See @ref{Dynamic Binding} for further details.
|
||||
|
||||
@node Dynamic Binding
|
||||
@subsection Dynamic Binding
|
||||
|
|
Loading…
Add table
Reference in a new issue