From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 46573@debbugs.gnu.org
Subject: bug#46573: 28.0.50; Error when edebugging setting unbound place
Date: Tue, 16 Feb 2021 23:51:28 +0100 [thread overview]
Message-ID: <87mtw3r5hr.fsf@gnus.org> (raw)
In-Reply-To: <87v9ar1w4l.fsf@web.de> (Michael Heerdegen's message of "Tue, 16 Feb 2021 23:32:58 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> when edebugging something like
>
> (setf PLACE VALUE)
>
> Edebug stops after PLACE and displays its "binding".
This is due to this definition:
;; Autoload this `put' since a user might use C-u C-M-x on an expression
;; containing a non-trivial `push' even before gv.el was loaded.
;;;###autoload
(put 'gv-place 'edebug-form-spec '(form)) ;So-called "indirect spec".
That's certainly not correct for the simplest forms like
(setf foo 'bar)
And it's not really correct for things like
(setf (gethash 1 table) 'bar)
either, is it? (Although it is amusing to see the results of
(gethash 1 table), it's not really helpful.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-02-16 22:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 22:32 bug#46573: 28.0.50; Error when edebugging setting unbound place Michael Heerdegen
2021-02-16 22:51 ` Lars Ingebrigtsen [this message]
2021-02-16 23:04 ` Stefan Monnier
2021-02-16 23:09 ` Lars Ingebrigtsen
2021-02-16 23:19 ` Lars Ingebrigtsen
2021-02-16 23:21 ` Lars Ingebrigtsen
2021-02-17 15:29 ` Eli Zaretskii
2021-03-01 21:17 ` Stefan Monnier
2021-03-02 5:58 ` Eli Zaretskii
2021-03-05 17:39 ` Stefan Monnier
2021-03-03 23:13 ` Michael Heerdegen
2021-03-03 23:26 ` Stefan Monnier
2021-03-03 23:47 ` Michael Heerdegen
2021-02-17 0:00 ` Stefan Monnier
2021-02-24 0:59 ` Gemini Lasswell
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=87mtw3r5hr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46573@debbugs.gnu.org \
--cc=michael_heerdegen@web.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).