From: "Y. E." via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50491@debbugs.gnu.org, yet@ego.team
Subject: bug#50491: 28.0.50; load-theme in early-init does not fully loads/enables expected faces
Date: Fri, 10 Sep 2021 13:28:49 +0300 [thread overview]
Message-ID: <m235qcg1we.fsf@ego.team> (raw)
In-Reply-To: <83fsudj7rl.fsf@gnu.org> (message from Eli Zaretskii on Fri, 10 Sep 2021 08:53:50 +0300)
Hi Eli,
> If you load themes only in init.el, once, without loading them in
> early-init.el, does the problem go away?
It is now, though I used to see "blinking" (white background showing up for
a second before a dark theme load) on Emacs startup with the theme
loaded/enabled in init.el.
Probably I saw it on one of the previously compiled Emacs versions.
> The early-init file is not meant to support every single
> customization of Emacs, only those that must be done before loading
> init.el.
Sure. I thought it might be a bug because a theme used to be loaded
correctly from early-init.el up until some (past) moment.
One question though.
`(emacs)49.4.6 The Early Init File' says:
"you can customize variables that affect frame appearance"
and
"customizations related to GUI features will not work reliably"
"frame appearance" and "GUI features" to my _naїve_ eyes _seem_
a bit contradictory.
Could probably documentation be clarified saying more on what exactly
is (not)supported in the early-init file?
For instance, which of these expressions are fine to be early-loaded:
`default-frame-alist', `initial-frame-alist', `inhibit-startup-message',
`initial-scratch-message', `scroll-bar-mode', `tool-bar-mode'?
> So if this works in init.el, then there's no bug here.
I'm fine with that since it works for me now with init.el.
Thank you,
YE
next prev parent reply other threads:[~2021-09-10 10:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 19:19 bug#50491: 28.0.50; load-theme in early-init does not fully loads/enables expected faces Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-10 5:53 ` Eli Zaretskii
2021-09-10 10:28 ` Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-09-10 10:57 ` Eli Zaretskii
2021-09-10 16:32 ` yet--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-10 18:03 ` Eli Zaretskii
2021-09-11 14:19 ` yet--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-11 14:27 ` Eli Zaretskii
2021-09-12 13:07 ` Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-12 13:21 ` Eli Zaretskii
2021-09-14 15:08 ` Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 10:22 ` bug#50491: [PATCH] " Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-16 12:41 ` Eli Zaretskii
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=m235qcg1we.fsf@ego.team \
--to=bug-gnu-emacs@gnu.org \
--cc=50491@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yet@ego.team \
--cc=yuga@ego.team \
/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).