unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: yet@ego.team
Cc: 50491@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#50491: 28.0.50; load-theme in early-init does not fully loads/enables expected faces
Date: Sat, 11 Sep 2021 17:27:45 +0300	[thread overview]
Message-ID: <83h7ergpb2.fsf@gnu.org> (raw)
In-Reply-To: <m2ee9vnqji.fsf@ego.team> (yet@ego.team)

> From: yet@ego.team
> Cc: 50491@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sat, 11 Sep 2021 17:19:13 +0300
> 
> 
> > We already say there:
> 
> >      We do not recommend that you move into ‘early-init.el’ customizations
> >   that can be left in the normal init files.  That is because the early
> > ...
> 
> > So it seems we already warn there against moving initializations to
> > early-init.el that can be left in init.el.  I see no reason to have a
> > more detailed warning.
> 
> That's right, I'm fine with that part.
> What confuses me is the phrase "frame appearance".

That could mean any number of things, and it is unreasonable to start
listing them, because the list will very quickly become outdated, aswe
add/change stuff in Emacs.

> It makes me guess if probably any of the documented
> `(elisp) 30.4 Frame Parameters' variables could be added
> to the early-init file quite "safely"?

I don't know, but why would you need to do that in early-init?  AFAIR,
startup.el already has all the necessary smarts to DTRT when the
user's init file changes frame parameters, so you shouldn't need to
move that into early-init file.  If you have specific problems with
changing them in the normal init files, please tell the details.





  reply	other threads:[~2021-09-11 14:27 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
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 [this message]
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=83h7ergpb2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50491@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).