all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gemini Lasswell <gazally@runbox.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22294@debbugs.gnu.org
Subject: bug#22294: Generating Edebug names for generic methods (was: bug#22294: Patch)
Date: Tue, 09 May 2017 22:07:57 -0700	[thread overview]
Message-ID: <87zielwb82.fsf_-_@runbox.com> (raw)
In-Reply-To: <d0c8724a-cea7-1f1d-7291-68002fe0bd59@yandex.ru> (Dmitry Gutov's message of "Mon, 8 May 2017 05:19:28 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> Unfortunately, this code fails when instrumenting a generic method
> (e.g. using C-u C-M-x) with something like:
>
> Unknown specializer foo@setf\ \(v\ \(_y\ \(eql\ 4\)\)\ z\)
>
> Any thoughts? edebug-match-method-args is definitely at fault there,
> but I'm not sure how to improve it.
>

Changing the return value of edebug-match-method-args from nil to
(list args) makes the error go away and the code sample from #24753
work. I haven't tested it beyond that.





  reply	other threads:[~2017-05-10  5:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 18:53 bug#22294: 25.0.50; edebug should support jumping into generic methods Dmitry Gutov
2017-03-03  2:52 ` Gemini Lasswell
2017-04-11 10:57   ` Dmitry Gutov
2017-04-26 23:12     ` bug#22294: Patch (was: bug#22294: 25.0.50; edebug should support jumping into generic methods) Gemini Lasswell
2017-05-07  2:34       ` bug#22294: Patch Dmitry Gutov
2017-05-07 20:28         ` Gemini Lasswell
2017-05-08  2:19           ` Dmitry Gutov
2017-05-10  5:07             ` Gemini Lasswell [this message]
2017-05-10 14:18               ` bug#22294: Generating Edebug names for generic methods Dmitry Gutov
2017-05-13 20:58                 ` Gemini Lasswell
2017-05-14  1:17                   ` Dmitry Gutov
2017-05-14 20:33                     ` Dmitry Gutov

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=87zielwb82.fsf_-_@runbox.com \
    --to=gazally@runbox.com \
    --cc=22294@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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.