From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
Xie Shynur <one.last.kiss@outlook.com>,
"61281@debbugs.gnu.org" <61281@debbugs.gnu.org>
Subject: bug#61281: “`(a \, b)” equals to “`(a . , b)”
Date: Tue, 07 Feb 2023 02:07:14 +0100 [thread overview]
Message-ID: <87ttzy8erh.fsf@web.de> (raw)
In-Reply-To: <SJ0PR10MB548834397BF46F527FE166B9F3DA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Mon, 6 Feb 2023 16:46:21 +0000")
Drew Adams <drew.adams@oracle.com> writes:
> > I recall one user had a need to macro-expand something that indented to
> > be passed to another macro-expand. We did not find a way to retain ","
> > in the macro-expanded sexp.
>
> Thanks. All the more reason why it would be good for the bug to be
> fixed. It may be a corner case, but apparently it really exists.
Unless I'm misunderstanding, this is a contradictory argument: to retain
a single "," for another macroexpand, you are actually _using_ this
implementation detail (in the outer expansion), so it is of no use to
change the ,X --> (\, X) expansion because then, the outer macro
expansion would handle the single "," as well.
And if the reader syntax "," was meant, this kind of "problem" exists in
other Lisps as well.
Michael.
next prev parent reply other threads:[~2023-02-07 1:07 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 23:23 bug#61281: “`(a \, b)” equals to “`(a . , b)” Xie Shynur
2023-02-04 23:34 ` Drew Adams
2023-02-04 23:43 ` Drew Adams
2023-02-05 0:28 ` Michael Heerdegen
2023-02-05 3:30 ` Drew Adams
2023-02-05 4:32 ` Michael Heerdegen
2023-02-05 4:55 ` Michael Heerdegen
2023-02-05 15:53 ` Drew Adams
2023-02-05 23:56 ` Michael Heerdegen
2023-02-06 2:26 ` Drew Adams
2023-02-06 3:03 ` Michael Heerdegen
2023-02-06 3:49 ` Drew Adams
2023-02-06 10:49 ` Ihor Radchenko
2023-02-06 16:46 ` Drew Adams
2023-02-07 1:07 ` Michael Heerdegen [this message]
2023-02-07 1:40 ` Michael Heerdegen
2023-02-07 11:50 ` bug#61281: Double backquote expansion and ", " (was: bug#61281: “`(a \, b)” equals to “`(a . , b)”) Ihor Radchenko
2023-02-07 23:33 ` bug#61281: Double backquote expansion and ", " Michael Heerdegen
2023-02-06 9:40 ` bug#61281: “`(a \, b)” equals to “`(a . , b)” Andreas Schwab
2023-02-06 16:43 ` Drew Adams
2023-02-07 8:56 ` Andreas Schwab
2023-02-07 18:00 ` Drew Adams
2023-02-07 23:44 ` Michael Heerdegen
2023-02-08 3:09 ` Drew Adams
2023-02-08 9:06 ` Andreas Schwab
2023-02-09 1:29 ` Michael Heerdegen
2023-02-09 2:04 ` Drew Adams
2023-02-09 2:15 ` Michael Heerdegen
2023-02-08 9:12 ` Andreas Schwab
2023-02-05 6:32 ` Jim Porter
2023-02-06 0:13 ` Michael Heerdegen
2023-02-06 0:18 ` Michael Heerdegen
2023-02-06 1:14 ` Jim Porter
2023-02-05 15:48 ` Drew Adams
2023-02-05 23:17 ` Michael Heerdegen
2023-02-06 1:49 ` Drew Adams
2023-02-06 4:11 ` Michael Heerdegen
2023-02-06 5:01 ` Drew Adams
2023-02-06 5:22 ` Drew Adams
2023-02-06 5:25 ` Michael Heerdegen
2023-02-06 16:43 ` Drew Adams
2023-02-07 2:00 ` Michael Heerdegen
2023-02-07 18:00 ` Drew Adams
2023-02-07 23:36 ` Michael Heerdegen
2023-02-08 3:09 ` Drew Adams
2023-02-09 1:37 ` Michael Heerdegen
2023-02-09 2:10 ` Drew Adams
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=87ttzy8erh.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=61281@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=one.last.kiss@outlook.com \
--cc=yantar92@posteo.net \
/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).