* doc/lispref/edebug.texi (Instrumenting Macro Calls): Use @defmac for macros.
This commit is contained in:
parent
33a9f380e5
commit
3a3bb90450
2 changed files with 6 additions and 2 deletions
|
|
@ -1,3 +1,7 @@
|
|||
2013-08-10 Xue Fuqiao <xfq.free@gmail.com>
|
||||
|
||||
* edebug.texi (Instrumenting Macro Calls): Use @defmac for macros.
|
||||
|
||||
2013-08-09 Xue Fuqiao <xfq.free@gmail.com>
|
||||
|
||||
* control.texi (Error Symbols): Minor fix for previous change.
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue