[Emacs-diffs] trunk r113784: * doc/lispref/edebug.texi (Instrumenting Macro Calls): Use @defmac for macros.

[Xue Fuqiao]

------------------------------------------------------------
revno: 113784
revision-id: address@hidden
parent: address@hidden
committer: Xue Fuqiao <address@hidden>
branch nick: trunk
timestamp: Sat 2013-08-10 13:03:11 +0800
message:
  * doc/lispref/edebug.texi (Instrumenting Macro Calls): Use @defmac for macros.
modified:
  doc/lispref/ChangeLog          changelog-20091113204419-o5vbwnq5f7feedwu-6155
  doc/lispref/edebug.texi        
edebug.texi-20091113204419-o5vbwnq5f7feedwu-6174

=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2013-08-09 22:34:05 +0000
+++ b/doc/lispref/ChangeLog     2013-08-10 05:03:11 +0000
@@ -1,3 +1,7 @@
+2013-08-10  Xue Fuqiao  <address@hidden>
+
+       * edebug.texi (Instrumenting Macro Calls): Use @defmac for macros.
+
 2013-08-09  Xue Fuqiao  <address@hidden>
 
        * control.texi (Error Symbols): Minor fix for previous change.

=== modified file 'doc/lispref/edebug.texi'
--- a/doc/lispref/edebug.texi   2013-01-01 09:11:05 +0000
+++ b/doc/lispref/edebug.texi   2013-08-10 05:03:11 +0000
@@ -1132,14 +1132,14 @@
 definitions in Lisp, but @code{def-edebug-spec} makes it possible to
 define Edebug specifications for special forms implemented in C.
 
address@hidden Macro def-edebug-spec macro specification
address@hidden 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.
address@hidden deffn
address@hidden defmac
 
 Here is a table of the possibilities for @var{specification} and how each
 directs processing of arguments.