unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: mail@xuchunyang.me
To: Federico Tedin <federicotedin@gmail.com>,
	"34065@debbugs.gnu.org" <34065@debbugs.gnu.org>
Subject: bug#34065: 26.1; Make edebug-eval-expression support code completion
Date: Wed, 20 Feb 2019 12:37:53 +0800	[thread overview]
Message-ID: <3031611550637473@sas1-19a94364928d.qloud-c.yandex.net> (raw)
In-Reply-To: <8736poyt0g.fsf@gmail.com>



20.01.2019, 10:15, "Federico Tedin" <federicotedin@gmail.com>:
> Xu Chunyang <mail@xuchunyang.me> writes:
>
>>  When type e (edebug-eval-expression) within Edebug, I notice there is no code completion, unlike
>>  M-: (eval-expression). So I wonder if edebug-eval-expression can behave
>>  like eval-expression, I guess simply replacing read-from-minibuffer with
>>  read--expression should work, though I've not tried.
>
> I've created a small patch which replaces `read-from-minibuffer' for
> `read--expression' in `edebug-eval-expression'. I would appreciate it if
> a maintainer could take a quick look.

I'm not a maintainer. Your patch looks good to me. Today I notice it's possible to change the interactive form via Advising Functions, so I plan to put the following to my init file until the patch is applied.

(define-advice edebug-eval-expression (:before (_expr) better-interactive-form)
  "Fix the original interactive form."
  (interactive (list (read--expression "Edebug Eval: "))))





  reply	other threads:[~2019-02-20  4:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  9:08 bug#34065: 26.1; Make edebug-eval-expression support code completion Xu Chunyang
2019-01-20  2:14 ` Federico Tedin
2019-02-20  4:37   ` mail [this message]
2019-03-12 23:14     ` Federico Tedin
2019-03-22  4:02       ` Stefan Monnier
2019-03-22 21:25       ` Federico Tedin

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=3031611550637473@sas1-19a94364928d.qloud-c.yandex.net \
    --to=mail@xuchunyang.me \
    --cc=34065@debbugs.gnu.org \
    --cc=federicotedin@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).