unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: yet--- 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 19:32:40 +0300	[thread overview]
Message-ID: <m2sfyc1jdj.fsf@ego.team> (raw)
In-Reply-To: <83sfycitpd.fsf@gnu.org> (message from Eli Zaretskii on Fri, 10 Sep 2021 13:57:34 +0300)


> > `(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?

> I'm not sure this is feasible in practice.  The general advice is not
> to customize in early-init stuff that can be customized in init.el.
> Any more detailed description runs the risk of describing side-effects
> of implementation details, which are therefore "subject to change
> without notice".

Yes, I understand.

Let's look at it at a bit different angle then,
to make sure there's really nothing to change in the documentation:

The documentation page 49.4.6 mentions that in early-init.el
we can customize two things:
1. "frame appearance".
2. "package initialization process".

After that, documentation goes into details on which exactly variables
can (for example) be customized for the goal of "package initialization
process". (4 variables are mentioned.)

Then it is said that "GUI features will not work reliably in early-init",
which leaves in me (then, potentially, in somebody else too) a cognitive
dis-balance (confusion), by contrasting with the phrase "frame appearance"
from the previous paragraph.

So I suggest considering (one of) the following changes:

- Clarify what "frame appearance" means (to distinguish from - probably
more abstract - term "GUI").

- Change word "appearance" to whatever is appropriate but doesn't
cause "GUI" connotations.

- Maybe provide a couple of example variables for "frame appearance",
similar to "package initialization process" examples. (If possible, of course).
  - My own assumption was I could "safely" use `default-frame-alist' and
  `initial-frame-alist' in early-init, but now I'm not sure.

- Or even remove "frame appearance" mentioning if it shouldn't be there
due to the reasoning given in the previous email (cited above).

- Maybe list all the variables that are surely supported and say more
definitively that anything not on that list are "subject to change
without notice".


Thank you for your work and for looking into it.

YE






  reply	other threads:[~2021-09-10 16:32 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
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 [this message]
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=m2sfyc1jdj.fsf@ego.team \
    --to=bug-gnu-emacs@gnu.org \
    --cc=50491@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=yet@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).