From: Teika Kazura <teika@gmx.com>
To: 62317@debbugs.gnu.org
Cc: eliz@gnu.org, monnier@iro.umontreal.ca
Subject: bug#62317: bug #62317: 28.2; This byte-compiled file behaves wrongly.
Date: Wed, 05 Apr 2023 13:12:41 +0900 (JST) [thread overview]
Message-ID: <20230405.131241.640176254664333647.teika@gmx.com> (raw)
In-Reply-To: <83o7o8yqhd.fsf@gnu.org> <jwv355jwple.fsf-monnier+emacs@gnu.org>
Thanks, that patch works for me. To be precise, I didn't byte-compile `bytecomp.el', (because it failed with batch-byte-compile) so instead I simply deleted bytecomp.elc.
BTW
> Admittedly, the resulting behavior can be very puzzling&frustrating for
> the user, which would tend to argue in favor of trying to at least
> detect the problem.
Good observation, ethologically and/or sociologically. :)
>> What surprises is that `native-compile-async' and `batch-native-compile' generate differnt codes.[...]
> This is not surprising at all[...]
IMHO a better bug-reporting guide seems desirable (or bug reporting "standard / protocol"). Or else, silly - censorship - untrained users like me will continue complaining, being a burden to developers. After all, coexistence of el, elc, and eln is too complicating.
Let me express my gratitude, Eli. Je vous remercie, Stefan; and Grazie to Andrea, though not cc-ed.
Best regards,
Teika
next prev parent reply other threads:[~2023-04-05 4:12 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
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 ` Teika Kazura [this message]
[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=20230405.131241.640176254664333647.teika@gmx.com \
--to=teika@gmx.com \
--cc=62317@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 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.