From 3a3bb90450d220c8fb336b80a9a4bdc5cc49a380 Mon Sep 17 00:00:00 2001 From: Xue Fuqiao Date: Sat, 10 Aug 2013 13:03:11 +0800 Subject: [PATCH] * doc/lispref/edebug.texi (Instrumenting Macro Calls): Use @defmac for macros. --- doc/lispref/ChangeLog | 4 ++++ doc/lispref/edebug.texi | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 5d140f72dbf..9d90a98a1ae 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,7 @@ +2013-08-10 Xue Fuqiao + + * edebug.texi (Instrumenting Macro Calls): Use @defmac for macros. + 2013-08-09 Xue Fuqiao * control.texi (Error Symbols): Minor fix for previous change. diff --git a/doc/lispref/edebug.texi b/doc/lispref/edebug.texi index 8e394b5d92d..8384c31a380 100644 --- a/doc/lispref/edebug.texi +++ b/doc/lispref/edebug.texi @@ -1132,14 +1132,14 @@ from the macro definition with @code{def-edebug-spec}. Adding definitions in Lisp, but @code{def-edebug-spec} makes it possible to define Edebug specifications for special forms implemented in C. -@deffn Macro def-edebug-spec macro specification +@defmac def-edebug-spec macro specification Specify which expressions of a call to macro @var{macro} are forms to be evaluated. @var{specification} should be the edebug specification. Neither argument is evaluated. The @var{macro} argument can actually be any symbol, not just a macro name. -@end deffn +@end defmac Here is a table of the possibilities for @var{specification} and how each directs processing of arguments. -- 2.39.2