From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: "Mattias Engdegård" <mattias.engdegard@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>,
68931@debbugs.gnu.org, jdc@uwo.ca
Subject: bug#68931: 30.0.50; Gnus byte-compilation error with (display . [not expire]) with git emacs
Date: Tue, 06 Feb 2024 15:46:30 -0500 [thread overview]
Message-ID: <jwvh6ile2zt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a5od1g0z.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 06 Feb 2024 12:42:04 -0800")
> In general I think Gnus goes to a lot of this kind of effort, based on
> performance considerations that are no longer current. Especially with
> native compilation available, I suspect there's no real need to keep
> byte-compiling things on the fly.
FWIW, I don't think native compilation makes any difference in this
respect since the purpose of the code is to avoid running
interpreted code, which is still as relevant with native compilation as
with byte compilation.
Stefan
next prev parent reply other threads:[~2024-02-06 20:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 22:11 bug#68931: 30.0.50; Gnus byte-compilation error with (display . [not expire]) with git emacs Dan Christensen
2024-02-05 12:50 ` Eli Zaretskii
2024-02-05 14:00 ` Mattias Engdegård
2024-02-05 14:32 ` Eli Zaretskii
2024-02-05 15:42 ` Eric Abrahamsen
2024-02-05 17:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 20:42 ` Eric Abrahamsen
2024-02-06 20:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-06 21:08 ` Eric Abrahamsen
2024-02-21 19:28 ` Dan Christensen
2024-02-21 22:05 ` Eric Abrahamsen
2024-03-03 2:30 ` Eric Abrahamsen
2024-02-05 14:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-05 17:13 ` Mattias Engdegård
2024-02-05 17:23 ` Dan Christensen
2024-02-05 19:12 ` 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
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=jwvh6ile2zt.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=68931@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=jdc@uwo.ca \
--cc=mattias.engdegard@gmail.com \
--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).