all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 16868@debbugs.gnu.org
Subject: bug#16868: Instrumenting macro for edebug turns it "not documented"
Date: Tue, 25 Feb 2014 14:37:59 -0500	[thread overview]
Message-ID: <1rppmbhtk8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAeL0STeMFk=sJPBD0LO3S1PjOw1KgaRth8-FqVVAD4j423tQA@mail.gmail.com> (Juanma Barranquero's message of "Mon, 24 Feb 2014 18:37:18 +0100")


Is it as simple as this?


*** lisp/emacs-lisp/edebug.el	2014-02-10 01:34:22 +0000
--- lisp/emacs-lisp/edebug.el	2014-02-25 19:35:39 +0000
***************
*** 1936,1946 ****
  	   [&optional stringp]
  	   [&optional ("interactive" interactive)]
  	   def-body))
- ;; FIXME? Isn't this missing the doc-string?  Cf defun.
  (def-edebug-spec defmacro
    ;; FIXME: Improve `declare' so we can Edebug gv-expander and
    ;; gv-setter declarations.
!   (&define name lambda-list [&optional ("declare" &rest sexp)] def-body))
  
  (def-edebug-spec arglist lambda-list)  ;; deprecated - use lambda-list.
  
--- 1936,1946 ----
  	   [&optional stringp]
  	   [&optional ("interactive" interactive)]
  	   def-body))
  (def-edebug-spec defmacro
    ;; FIXME: Improve `declare' so we can Edebug gv-expander and
    ;; gv-setter declarations.
!   (&define name lambda-list [&optional stringp]
!            [&optional ("declare" &rest sexp)] def-body))
  
  (def-edebug-spec arglist lambda-list)  ;; deprecated - use lambda-list.
  






  reply	other threads:[~2014-02-25 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 17:37 bug#16868: Instrumenting macro for edebug turns it "not documented" Juanma Barranquero
2014-02-25 19:37 ` Glenn Morris [this message]
2014-02-25 20:49   ` Juanma Barranquero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1rppmbhtk8.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=16868@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.