From: Michael Heerdegen <michael_heerdegen@web.de>
To: Alan Mackenzie <acm@muc.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 59213@debbugs.gnu.org
Subject: bug#59213: Emacs 29: Edebug fails to instrument a parameter whose name begins with _
Date: Mon, 14 Nov 2022 03:48:45 +0100 [thread overview]
Message-ID: <87h6z2tfn6.fsf@web.de> (raw)
In-Reply-To: <Y29o/uABZE7n/u/3@ACM> (Alan Mackenzie's message of "Sat, 12 Nov 2022 09:35:58 +0000")
Alan Mackenzie <acm@muc.de> writes:
> During the edebug session, I attempted
>
> e _old-len RET.
>
> Instead of giving me the value of _old-len (which was 3) it gave the
> error message
>
> Error: Symbol's value as variable is void: _old-len
Here is a test case:
(defun test (a b _c)
(+ a b))
Instrument, etc., and e _c RET gives you the void variable error.
I don't think this behavior is intended.
When I change
(defun edebug-eval (expr)
(backtrace-eval expr 0 'edebug-after))
to
(defun edebug-eval (expr)
(backtrace-eval expr 1 'edebug-after))
;; ^
a binding of _c is being printed. Let's CC Stefan who is the real
expert and ask whether this change would make sense. I'm not sure when
and in which frames a binding is or should be visible. Note: when _c is
used in the function body a binding _is_ visible also in the 0th frame.
Michael.
next prev parent reply other threads:[~2022-11-14 2:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 9:35 bug#59213: Emacs 29: Edebug fails to instrument a parameter whose name begins with _ Alan Mackenzie
2022-11-14 2:48 ` Michael Heerdegen [this message]
2022-11-14 3:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 10:28 ` Alan Mackenzie
2022-11-14 12:50 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 12:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10 18:51 ` Alan Mackenzie
2023-02-10 22:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-11 7:26 ` Eli Zaretskii
2023-02-13 3:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-13 12:54 ` Eli Zaretskii
2023-02-11 11:17 ` Alan Mackenzie
2023-02-14 21:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14 22:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 18:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 18:46 ` Alan Mackenzie
2023-02-20 22:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-15 13:08 ` Eli Zaretskii
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=87h6z2tfn6.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=59213@debbugs.gnu.org \
--cc=acm@muc.de \
--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 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).