Subject: bug#69431: 30.0.50; Strange fontificaion behavior

From: Ihor Radchenko <[email-masked]>
Date: Sat, 06 Apr 2024 18:38:22 +0000

Andrea Corallo <[email-masked]> writes:

> If I remove the invocations of 'emacs-lisp-compilation-mode' from
> 'comp-run-async-workers' my org file gets fontified correctly.
> ...
>   k-variable-watcher(font-lock-keywords ... set #<buffer test.org>)
> ...
>   global-font-lock-mode-enable-in-buffers()
>   run-hooks(after-change-major-mode-hook)
>   run-mode-hooks(emacs-lisp-compilation-mode-hook)
>   emacs-lisp-compilation-mode()
>   comp-run-async-workers()
>   native--compile-async("/home/andcor03/emacs2/lisp/net/dbus.el" nil late)
> ...
>   require(dbus)
> ...
>   org-load-modules-maybe()
>   org-mode()
> ...
>   find-file-noselect-1(#<buffer test.org> "~/test.org" nil nil "~/test.org" (14180533 64513))

IMHO, it looks like bug#58888 - global font-lock-mode is enabled in the
middle of major mode initialization and messes things up.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>