summaryrefslogtreecommitdiff
path: root/doc/lispref/functions.texi
diff options
context:
space:
mode:
authorGlenn Morris <rgm@gnu.org>2018-02-02 07:50:22 -0800
committerGlenn Morris <rgm@gnu.org>2018-02-02 07:50:22 -0800
commita893a4db20e9a6cf6a03855d40d9b9dfd9c49139 (patch)
treedc27e36bb663ee054a33d99e5647c0d152e853d8 /doc/lispref/functions.texi
parent8dd2edc70fe77e86d0b4a9928e7f5bcd2543947a (diff)
parent6f495abd0d65075714f92b0eb7f637d6f540edfa (diff)
downloademacs-a893a4db20e9a6cf6a03855d40d9b9dfd9c49139.tar.gz
Merge from origin/emacs-26
6f495ab (origin/emacs-26) Another round of manual fixups 59344c4 * doc/lispref/customize.texi (Custom Themes): Clarify .el pre... 6386efc * doc/emacs/entering.texi (Entering Emacs): Another wording fix. e21f018 * doc/lispref/functions.texi (Inline Functions): Fix typo (Bu... 1c2fb04 * lisp/imenu.el (imenu-generic-expression): Rephrase doc (Bug... b90e91c Fix last change of @key markup f180075 * doc/emacs/entering.texi (Entering Emacs): Fix markup.
Diffstat (limited to 'doc/lispref/functions.texi')
-rw-r--r--doc/lispref/functions.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index c3e5dc0eb5b..9090956d837 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -2098,7 +2098,7 @@ to verify that using @code{defun} actually has performance problems.
After an inline function is defined, its inline expansion can be
performed later on in the same file, just like macros.
- It's possible to use @code{defsubst} to define a macro to expand
+ It's possible to use @code{defmacro} to define a macro to expand
into the same code that an inline function would execute
(@pxref{Macros}). But the macro would be limited to direct use in
expressions---a macro cannot be called with @code{apply},