unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 46573@debbugs.gnu.org
Subject: bug#46573: 28.0.50; Error when edebugging setting unbound place
Date: Tue, 16 Feb 2021 18:04:41 -0500	[thread overview]
Message-ID: <jwvk0r7y5tw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mtw3r5hr.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 16 Feb 2021 23:51:28 +0100")

>> when edebugging something like
>>
>>   (setf PLACE VALUE)
>>
>> Edebug stops after PLACE and displays its "binding". 

Hmm... looks like we have a bug.

> 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

This has been there since the introduction of `gv`, so I think it
*is* correct.  The problem is elsewhere (likely introduced by some of
my recent changes to Edebug).


        Stefan






  reply	other threads:[~2021-02-16 23:04 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
2021-02-16 23:04   ` Stefan Monnier [this message]
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=jwvk0r7y5tw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=46573@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.de \
    /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).