From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, mail@xuchunyang.me, 34975@debbugs.gnu.org
Subject: bug#34975: 26.1.92; In backquote, the comma marker does not work with variable name started with dot
Date: Thu, 04 Apr 2019 09:25:48 -0400 [thread overview]
Message-ID: <87mul5ewbn.fsf@gmail.com> (raw)
In-Reply-To: <83mul5dih0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 04 Apr 2019 16:10:19 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Noam Postavsky <npostavs@gmail.com>
>> Date: Wed, 03 Apr 2019 23:31:24 -0400
>> Cc: Xu Chunyang <mail@xuchunyang.me>, 34975@debbugs.gnu.org
>>
>> There's also Bug#19790 about this. I think it makes sense to just
>> remove this reader macro, as far as I can tell, nobody really wants this
>> destructive splicing feature.
>
> How hard would it be fixing it? I'm uneasy with removing features
> because we are confused about them.
The destructive splicing feature was never added though. Only the
reader macro part. But if you're asking about possible breakage, then
yes, it's possible that someone out there wrote a macro which gives some
semantics to ",.", like pcase gives its own semantics to "`" and ",".
next prev parent reply other threads:[~2019-04-04 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 14:19 bug#34975: 26.1.92; In backquote, the comma marker does not work with variable name started with dot Xu Chunyang
2019-03-24 15:16 ` Michael Heerdegen
2019-03-25 0:06 ` Drew Adams
2019-03-25 1:33 ` Michael Heerdegen
2019-03-25 14:21 ` Drew Adams
2019-03-26 0:03 ` Michael Heerdegen
2019-03-26 9:49 ` Andreas Schwab
2019-03-27 1:50 ` Michael Heerdegen
2019-04-04 3:31 ` Noam Postavsky
2019-04-04 13:10 ` Eli Zaretskii
2019-04-04 13:25 ` Noam Postavsky [this message]
2019-04-04 22:28 ` Basil L. Contovounesios
2019-04-04 23:37 ` Noam Postavsky
2019-04-05 1:15 ` Basil L. Contovounesios
2019-04-05 6:21 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mul5ewbn.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=34975@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mail@xuchunyang.me \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.