From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gemini Lasswell <gazally@runbox.com>, 25077@debbugs.gnu.org
Subject: bug#25077: 25.1; Incorrect Edebug spec for c-lang-defvar
Date: Sat, 4 Feb 2017 16:23:07 +0000 [thread overview]
Message-ID: <20170204162307.GC2047__14392.5817487345$1486225491$gmane$org@acm> (raw)
In-Reply-To: <83h94a8aby.fsf@gnu.org>
Hello, Eli.
On Sat, Feb 04, 2017 at 13:27:45 +0200, Eli Zaretskii wrote:
> > From: Gemini Lasswell <gazally@runbox.com>
> > Date: Wed, 30 Nov 2016 11:20:28 -0800
> >
> > The Edebug spec for c-lang-defvar doesn't allow for the use of
> > 'dont-doc, which prevents the use of Edebug and Testcover on
> > cc-langs.el.
> >
> > To reproduce, using emacs -Q starting at the root of the Emacs
> > sources:
> >
> > M-: (require 'cc-langs) RET
> > C-x C-f lisp/progmodes/cc-langs.el RET
> > C-s dont-doc RET
> > C-u C-M-x
> >
> > Result: edebug-syntax-error: Invalid read syntax: stringp, "failed"
> >
> > I tried this change to the Edebug spec for c-lang-defvar, and it makes
> > Edebug work on all the c-lang-defvar uses in this file:
> >
> > (def-edebug-spec c-lang-defvar
> > (&define name def-form &optional &or ("quote" "dont-doc") stringp))
> >
> > Alternatively, the 'dont-doc could be removed from the 7 places it is
> > used. The majority of c-lang-defvar calls simply omit the docstring,
> > and the code in c-lang-defvar is not doing any checking for dont-doc,
> > it simply ignores that parameter if it is not a string.
> Alan, could you please look into this?
Yes, I will.
> Thanks.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-02-04 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 19:20 bug#25077: 25.1; Incorrect Edebug spec for c-lang-defvar Gemini Lasswell
2017-02-04 11:27 ` Eli Zaretskii
2017-02-04 16:23 ` Alan Mackenzie [this message]
2017-02-18 16:10 ` Alan Mackenzie
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='20170204162307.GC2047__14392.5817487345$1486225491$gmane$org@acm' \
--to=acm@muc.de \
--cc=25077@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gazally@runbox.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.