From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: zshaftel@gmail.com, 42499@debbugs.gnu.org
Subject: bug#42499: [PATCH] Add Bytecode Offset information to Backtrace
Date: Sun, 18 Oct 2020 10:11:33 +0200 [thread overview]
Message-ID: <87h7qskl6y.fsf@gnus.org> (raw)
In-Reply-To: <83h7qttcxw.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Oct 2020 12:32:43 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I don't think we should start dismissing .elc compiled files just
> because native compilation is on the horizon. Some users might
> legitimately decide they don't want their Lisp natively-compiled, or
> may be unable to do so because of the GCC version they have
> installed. We should continue supporting byte-compilation features
> for the next few versions at least.
Yes, of course. The only question is whether it makes sense to add new,
advanced features that is only relevant for .elc files at this point
> I have an email from Craig in late August saying the disclaimer is
> being submitted to legal. Suggest to ping Craig about this.
Will do.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-18 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 23:29 bug#42499: [PATCH] Add Bytecode Offset information to Backtrace Zach Shaftel
2020-10-17 9:08 ` Lars Ingebrigtsen
2020-10-17 9:32 ` Eli Zaretskii
2020-10-18 4:15 ` Richard Stallman
2020-10-18 8:11 ` Lars Ingebrigtsen [this message]
2020-10-18 15:03 ` Eli Zaretskii
2021-05-13 9:54 ` Lars Ingebrigtsen
2021-05-13 10:25 ` Eli Zaretskii
2021-06-12 12:14 ` Lars Ingebrigtsen
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=87h7qskl6y.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=42499@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=zshaftel@gmail.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).