all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 22294@debbugs.gnu.org
Subject: bug#22294: Generating Edebug names for generic methods
Date: Wed, 10 May 2017 17:18:42 +0300	[thread overview]
Message-ID: <3070039f-caf2-3e58-e3d3-afb8eac5152f@yandex.ru> (raw)
In-Reply-To: <87zielwb82.fsf_-_@runbox.com>

On 10.05.2017 8:07, Gemini Lasswell wrote:

> 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.

Thanks! I only tried `args' (without (list)). My only excuse is that it 
was late at night.

So, what do you think about this modification?

It works well in my testing, and it avoids introducing the dynamic 
variable. I'll commit it in your name (since you did most of the work 
anyway) if you like it.





  reply	other threads:[~2017-05-10 14:18 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             ` bug#22294: Generating Edebug names for generic methods (was: bug#22294: Patch) Gemini Lasswell
2017-05-10 14:18               ` Dmitry Gutov [this message]
2017-05-13 20:58                 ` bug#22294: Generating Edebug names for generic methods 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=3070039f-caf2-3e58-e3d3-afb8eac5152f@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=22294@debbugs.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.