From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, 69431@debbugs.gnu.org
Subject: bug#69431: 30.0.50; Strange fontificaion behavior
Date: Wed, 28 Feb 2024 04:20:13 +0900 [thread overview]
Message-ID: <87wmqpsoia.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <86il29u4hy.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 27 Feb 2024 20:49:29 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Ihor Radchenko <yantar92@posteo.net>
>> Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>, 69431@debbugs.gnu.org
>> Date: Tue, 27 Feb 2024 17:58:16 +0000
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > I cannot reproduce this with today's master branch. I see "* Foo"
>> > fontified with org-level-1 face.
>> >
>> > Maybe this is platform-dependent?
>>
>> I can reproduce using the latest master (with make bootstrap), using the
>> same steps.
>
> I don't want to bootstrap for this, but I removed all *.elc files from
> the lisp/org/ directory and rebuilt, and I still cannot reproduce.
>
>> I cannot reproduce when changing the load path to Org git
>> folder ( main, bugfix branches, and Org 9.6.15 tag which should be the
>> same with Emacs built-in version).
>
> So maybe the problem is already solved somehow?
I found a bit more about this. If build with --native-compilation=no, I
can't reproduce, and at least --native-compilation=aot can reproduce.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2024-02-27 19:20 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 16:58 bug#69431: 30.0.50; Strange fontificaion behavior OGAWA Hirofumi
2024-02-27 17:29 ` Eli Zaretskii
2024-02-27 17:58 ` Ihor Radchenko
2024-02-27 18:49 ` Eli Zaretskii
2024-02-27 19:20 ` OGAWA Hirofumi [this message]
2024-02-27 19:26 ` Ihor Radchenko
2024-02-27 19:33 ` Eli Zaretskii
2024-02-27 20:11 ` Andrea Corallo
2024-02-27 20:23 ` OGAWA Hirofumi
2024-02-27 20:24 ` Ihor Radchenko
2024-02-27 20:27 ` Ihor Radchenko
2024-02-27 21:48 ` Andrea Corallo
2024-02-28 12:00 ` Ihor Radchenko
[not found] ` <87v869h86b.fsf@>
2024-02-28 13:53 ` Andrea Corallo
2024-02-28 16:57 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87zfvkfrw0.fsf@>
2024-02-28 18:44 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-28 19:34 ` Andrea Corallo
2024-02-28 21:41 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87jzmofes3.fsf@>
2024-02-29 22:16 ` Andrea Corallo
2024-03-01 1:13 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 1:18 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-03 16:20 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87bk7vgucb.fsf@>
2024-03-03 17:01 ` Andrea Corallo
2024-03-06 16:38 ` Andrea Corallo
2024-03-07 11:59 ` OGAWA Hirofumi
2024-03-07 14:49 ` Andrea Corallo
2024-03-07 22:33 ` Andrea Corallo
2024-03-21 8:32 ` Eli Zaretskii
2024-03-23 19:29 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87frwgeohj.fsf@>
2024-03-23 20:34 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-23 20:34 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-24 9:12 ` Andrea Corallo
2024-03-24 9:28 ` Eli Zaretskii
2024-03-26 21:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-27 8:31 ` Andrea Corallo
2024-03-27 14:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 19:49 ` Andrea Corallo
2024-03-31 20:40 ` Andrea Corallo
2024-04-01 10:59 ` Ihor Radchenko
2024-04-01 12:33 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 17:01 ` Andrea Corallo
2024-04-06 18:38 ` Ihor Radchenko
2024-04-07 7:47 ` Andrea Corallo
[not found] ` <87plv1v3za.fsf@>
2024-04-07 11:46 ` Eli Zaretskii
2024-04-07 12:01 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <875xwtidpn.fsf@>
2024-04-07 12:48 ` Eli Zaretskii
[not found] ` <871q7hi5f9.fsf@>
2024-04-07 15:50 ` Eli Zaretskii
2024-04-07 18:02 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87v84tgifz.fsf@>
2024-04-07 18:35 ` Eli Zaretskii
2024-04-07 19:09 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-08 7:15 ` Andrea Corallo
2024-04-08 11:40 ` Eli Zaretskii
2024-04-07 12:29 ` Andrea Corallo
2024-04-07 15:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-08 7:00 ` Andrea Corallo
2024-04-08 12:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 14:31 ` Ihor Radchenko
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=87wmqpsoia.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=69431@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yantar92@posteo.net \
/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).