unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Gemini Lasswell <gazally@runbox.com>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	46573@debbugs.gnu.org
Subject: bug#46573: 28.0.50; Error when edebugging setting unbound place
Date: Thu, 04 Mar 2021 00:47:08 +0100	[thread overview]
Message-ID: <87blbzn6kj.fsf@web.de> (raw)
In-Reply-To: <jwvblbzomd9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 03 Mar 2021 18:26:12 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Maybe we should add a special case for when `setf` is used for
> a simple variable such that the variable is not instrumented at all,
> just as is the case for `setq`?

I don't know.  Maybe not.

When the value expression is a list, i.e. not something self-evaluating
like an number, the behavior doesn't seem so strange anymore to me, it
makes sense.  And my gut feeling is that it would be more confusing to
handle different place expressions differently than setq and setf.

So the fix is ok from my side.  Thanks for the clarification.

Regards,

Michael.





  reply	other threads:[~2021-03-03 23:47 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
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 [this message]
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=87blbzn6kj.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=46573@debbugs.gnu.org \
    --cc=gazally@runbox.com \
    --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 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).