From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "69533@debbugs.gnu.org" <69533@debbugs.gnu.org>,
"rms@gnu.org" <rms@gnu.org>
Subject: bug#69533: 30.0.50; Wrong byte compilation of a certain apply syntax
Date: Mon, 4 Mar 2024 15:52:20 +0000 [thread overview]
Message-ID: <SJ0PR10MB54887D16DC3A9F27763309F6F3232@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87a5nesj7f.fsf@web.de>
> Drew Adams writes:
>
> > FWIW, I'm very surprised to find this "feature".
> > That it's documented suggests it was intended.
> > But I don't know why it would be. Does anyone?
>
> Bug#40968 I think.
Yes, thanks. I'd forgotten about that,
and that I'd contributed to the thread.
I agree with what I said there ;-),
which is not always the case. ;-)
In particular this:
Pip>> I think there's consensus, then.
me> FTR, FWIW: Not a consensus that includes me.
me> I'm in favor of making an incompatible
me> change, to align Emacs with Common Lisp's
me> more reasonable behavior.
I might have added every other Lisp; it's
not just Common Lisp, AFAIK.
No one has given a good reason _why_ Elisp
ever had this one-off (no other Lisp has
it) behavior, AFAICS.
There's no reason given in that thread.
The thread just concentrates on "fixing"
the odd-ball "special" case. And the fix
was to mention that case in the doc.
Really too bad.
next prev parent reply other threads:[~2024-03-04 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 1:51 bug#69533: 30.0.50; Wrong byte compilation of a certain apply syntax Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-04 3:39 ` Drew Adams
2024-03-04 4:40 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-04 15:52 ` Drew Adams [this message]
2024-03-04 5:13 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-04 7:46 ` Basil L. Contovounesios
2024-03-04 8:10 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-04 8:47 ` Basil L. Contovounesios
2024-03-04 8:17 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-04 8:48 ` Basil L. Contovounesios
2024-03-04 9:39 ` Andreas Schwab
2024-03-04 12:52 ` Basil L. Contovounesios
2024-03-04 13:13 ` Mattias Engdegård
2024-03-04 13:25 ` Mattias Engdegård
2024-03-04 21:12 ` Drew Adams
2024-03-14 7:52 ` Eli Zaretskii
2024-03-14 8:44 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-14 11:13 ` Eli Zaretskii
2024-03-14 11:18 ` Mattias Engdegård
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=SJ0PR10MB54887D16DC3A9F27763309F6F3232@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=69533@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=rms@gnu.org \
/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).