From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 25117@debbugs.gnu.org
Subject: bug#25117: 25.1.90; Result of called-interactively-p differs WRT file contents
Date: Mon, 21 Oct 2019 15:21:24 +0200 [thread overview]
Message-ID: <87r236nsiz.fsf@web.de> (raw)
In-Reply-To: <jwvtv82p9zk.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 21 Oct 2019 08:21:15 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Sounds right, yes. It should be a small matter of accepting `closure`
> additionally to `lambda` (and then account for the fact that the arg
> list is one step further in that case).
I tried that locally, but it's broken worse, and it's broken also for
the dynamical binding mode case.
Seems edebug-enter has to be replaced with edebug-default-enter (or are
both cases possible?). Even then, i.e. when
edebug--called-interactively-skip returns 2 (and I ran everything with
compiled files) `called-interactively-p' still returns nil. I gave up
for now.
Michael.
next prev parent reply other threads:[~2019-10-21 13:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 13:01 bug#25117: 25.1.90; Result of called-interactively-p differs WRT file contents Andreas Röhler
2016-12-05 16:18 ` Michael Heerdegen
2016-12-05 16:58 ` Andreas Röhler
2016-12-05 16:58 ` Michael Heerdegen
2016-12-05 17:18 ` Andreas Röhler
2016-12-05 17:39 ` Michael Heerdegen
2016-12-05 18:23 ` Andreas Röhler
2016-12-05 19:08 ` Noam Postavsky
2016-12-05 19:38 ` Andreas Röhler
2016-12-05 19:34 ` Noam Postavsky
2016-12-05 19:52 ` Andreas Röhler
2016-12-05 19:51 ` Noam Postavsky
2016-12-05 20:09 ` Andreas Röhler
2019-10-20 21:34 ` Lars Ingebrigtsen
2019-10-21 9:15 ` Michael Heerdegen
2019-10-21 12:21 ` Stefan Monnier
2019-10-21 13:21 ` Michael Heerdegen [this message]
2022-04-18 11:24 ` bug#25117: 25.1.90; `called-interactively-p' from edebug with lexical-binding always gives nil Lars Ingebrigtsen
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=87r236nsiz.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=25117@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.