From: Eli Zaretskii <eliz@gnu.org>
To: Teika Kazura <teika@gmx.com>, Andrea Corallo <akrl@sdf.org>
Cc: 62317@debbugs.gnu.org
Subject: bug#62317: bug #62317: 28.2; This byte-compiled file behaves wrongly.
Date: Tue, 28 Mar 2023 15:08:16 +0300 [thread overview]
Message-ID: <83a5zx84en.fsf@gnu.org> (raw)
In-Reply-To: <20230328.181544.1322854406210586127.teika@gmx.com> (message from Teika Kazura on Tue, 28 Mar 2023 18:15:44 +0900 (JST))
> Date: Tue, 28 Mar 2023 18:15:44 +0900 (JST)
> From: Teika Kazura <teika@gmx.com>
>
> This bug is also related to native-compilation, but I can't demonstrate it in a simple way.
>
> The situation for the init.el that I really use is:
> * I suspect that the pair of require - set-buffer causes the bug. At least, the above workaround works, wrapping set-buffer.
> * There the existence of init.elc does not matter. Instead, the init-<hash>.eln is the problem. By removing it, the bug disappears.
> * But each time I run emacs, an eln is automatically generated aynchronously if it's lacking. (I can't find what causes automatic native compilation.)
Native compilation is always triggered when Emacs loads a .elc file
for which there is no corresponding .eln.
> Anyway fixing this bug will solve other native-compilation related bugs, if any.
CC'ing Andrea.
next prev parent reply other threads:[~2023-03-28 12:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 3:54 bug#62317: 28.2; This byte-compiled file behaves wrongly Teika Kazura
2023-03-22 6:39 ` bug#62317: bug #62317: " Teika Kazura
2023-03-28 9:15 ` Teika Kazura
2023-03-28 12:08 ` Eli Zaretskii [this message]
2023-03-28 12:43 ` Andrea Corallo
2023-03-28 12:53 ` Eli Zaretskii
2023-03-28 13:49 ` Andrea Corallo
2023-03-30 9:20 ` Teika Kazura
2023-03-30 9:41 ` Eli Zaretskii
2023-04-01 7:36 ` Teika Kazura
2023-04-01 8:08 ` Eli Zaretskii
2023-04-01 16:27 ` bug#62317: " Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-01 17:10 ` Eli Zaretskii
2023-04-01 23:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-02 5:17 ` Eli Zaretskii
2023-09-12 0:08 ` Stefan Kangas
2023-09-12 18:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 14:02 ` Stefan Kangas
2023-09-13 14:45 ` Eli Zaretskii
2023-09-13 15:46 ` Stefan Kangas
2023-04-01 23:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 0:09 ` Stefan Kangas
2023-04-05 4:12 ` bug#62317: bug #62317: " Teika Kazura
[not found] ` <handler.62317.C.169462003624017.notifdonectrl.0@debbugs.gnu.org>
2023-09-14 6:35 ` bug#62317: acknowledged by developer Teika Kazura
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=83a5zx84en.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62317@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=teika@gmx.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 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.