diff options
author | Lute Kamstra <lute@gnu.org> | 2005-03-15 17:27:28 +0000 |
---|---|---|
committer | Lute Kamstra <lute@gnu.org> | 2005-03-15 17:27:28 +0000 |
commit | 8f9662e36bc9e24d03a31b2cfc296487a76d3b51 (patch) | |
tree | 461b115b094cb300c5aca116894009dcc9982a39 /lispref/edebug.texi | |
parent | 381979f76be4d5c280d09c0d604f0ca4eb14b5e7 (diff) | |
download | emacs-8f9662e36bc9e24d03a31b2cfc296487a76d3b51.tar.gz |
(Instrumenting Macro Calls): Fix typos.
Diffstat (limited to 'lispref/edebug.texi')
-rw-r--r-- | lispref/edebug.texi | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/lispref/edebug.texi b/lispref/edebug.texi index e34549cccb1..a007f81dcfb 100644 --- a/lispref/edebug.texi +++ b/lispref/edebug.texi @@ -1074,7 +1074,7 @@ time later.) Therefore, you must define an Edebug specification for each macro that Edebug will encounter, to explain the format of calls to that -macro. To do this, add an @code{edebug} declaration to the macro +macro. To do this, add a @code{debug} declaration to the macro definition. Here is a simple example that shows the specification for the @code{for} example macro (@pxref{Argument Evaluation}). @@ -1095,10 +1095,9 @@ the @code{declare} form. You can also define an edebug specification for a macro separately from the macro definition with @code{def-edebug-spec}. Adding -@code{edebug} declarations is preferred, and more convenient, for -macro definitions in Lisp, but @code{def-edebug-spec} makes it -possible to define Edebug specifications for special forms implemented -in C. +@code{debug} declarations is preferred, and more convenient, for macro +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 Specify which expressions of a call to macro @var{macro} are forms to be |