From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 56739@debbugs.gnu.org, Wing Hei Chan <whmunkchan@outlook.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#56739: 29.0.50; `cl-psetq' and `cl-psetf' fail to recognize symbol macros
Date: Mon, 05 Sep 2022 21:14:35 +0200 [thread overview]
Message-ID: <87zgfdzl9g.fsf@gnus.org> (raw)
In-Reply-To: <87y1w6xjmg.fsf@web.de> (Michael Heerdegen's message of "Wed, 03 Aug 2022 02:20:55 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> I think we can fix this (both cases mentioned) similarly as in cl-letf:
>
> From 29ea21a751ab6e71b2fb34c781131e31fc7b950d Mon Sep 17 00:00:00 2001
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Wed, 3 Aug 2022 02:06:16 +0200
> Subject: [PATCH] WIP: Fix symbol macros used in cl-psetf (Bug#56739)
This was a month ago, but as far as I can tell, this patch was never
pushed.
Perhaps Stefan has some comments here; added to the CCs.
next prev parent reply other threads:[~2022-09-05 19:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 12:12 bug#56739: 29.0.50; `cl-psetq' and `cl-psetf' fail to recognize symbol macros Wing Hei Chan
2022-08-02 2:41 ` Michael Heerdegen
2022-08-02 23:59 ` Michael Heerdegen
2022-08-03 0:20 ` Michael Heerdegen
2022-09-05 19:14 ` Lars Ingebrigtsen [this message]
2022-09-06 1:29 ` Michael Heerdegen
2022-09-06 2:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 18:31 ` Stefan Kangas
2023-09-08 3:07 ` Michael Heerdegen
2023-09-09 6:12 ` Michael Heerdegen
2023-09-09 7:08 ` Gerd Möllmann
[not found] ` <f49326d6-85e2-4fed-83ae-815a82cefe30@outlook.com>
2023-09-09 8:03 ` Wing Hei Chan
2023-09-09 9:24 ` Gerd Möllmann
2023-09-09 15:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 16:33 ` Gerd Möllmann
2022-09-06 2:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87zgfdzl9g.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=56739@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=whmunkchan@outlook.com \
/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).