all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62317@debbugs.gnu.org, Teika Kazura <teika@gmx.com>
Subject: bug#62317: bug #62317: 28.2; This byte-compiled file behaves wrongly.
Date: Tue, 28 Mar 2023 12:43:33 +0000	[thread overview]
Message-ID: <xjfa5zxgi6i.fsf@ma.sdf.org> (raw)
In-Reply-To: <83a5zx84en.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 28 Mar 2023 15:08:16 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> 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.

Yes, I guess it's all caused by
263d6c38539691c954f4c3057cbe8d5468499b91.

I'm in a business trip now but I want to fix it ASAP (within the week),
I already started to look into it.

Anyway if we feel this is causing too much disruption I'm happy to
revert the offending commit now WDYT?

Thanks

  Andrea





  reply	other threads:[~2023-03-28 12:43 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
2023-03-28 12:43     ` Andrea Corallo [this message]
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=xjfa5zxgi6i.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=62317@debbugs.gnu.org \
    --cc=eliz@gnu.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.