unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
Subject: RE: About early-init right use.
Date: Tue, 2 Apr 2019 10:57:59 -0700 (PDT)	[thread overview]
Message-ID: <f69229de-9013-4c5e-a692-7c11718721fb@default> (raw)
In-Reply-To: <jwvy34swd9s.fsf-monnier+emacs@gnu.org>

> > Seems a bit contradictory wrt "variables that affect frame
> > appearance".  What variables are we talking about, if they
> > are not "related to GUI features"?
> 
> If you can improve the wording it would help.  Indeed "related" is not
> precise enough.
> 
> Since the GUI is initialized after loading the early-init.el, you can't
> (yet) *ask* Emacs about the GUI (e.g. `window-system` will give you the
> wrong info, frame sizes won't be right either, ...), but you can *tell*
> Emacs about GUI-related settings like `(setq default-frame-alist ...)`.
> 
> You also can't use your installed packages from early-init.el because
> they haven't been activated yet (tho you can manually activate them by
> calling `package-activate-all`, of course).

Maybe say that.  If there is a good reason why you
would define some "variables that affect frame
appearance" in the early file then maybe provide
that.

It's not because one _can_ define variables there
that one should do so, in general.  But if there
are particular cases where it might be _better_
to do it in the early file then maybe mention them.

In general, it needs to be made clear why you might
better put something in the early file (and perhaps
give some examples), and state the general guideline
that otherwise you should put everything in the
"late" file.



      reply	other threads:[~2019-04-02 17:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190401235436.2cnhvuxzdj635hpn.ref@Ergus>
2019-04-01 23:54 ` About early-init right use Ergus
2019-04-02  6:39   ` tomas
2019-04-02 14:21     ` Drew Adams
2019-04-02 15:42       ` tomas
2019-04-02 16:55         ` Ergus
2019-04-02 17:26           ` tomas
2019-04-02 18:40           ` Stefan Monnier
2019-04-03 17:21             ` Lele Gaifax
2019-04-03 17:28               ` Stefan Monnier
2019-04-03 17:43                 ` Lele Gaifax
2019-04-04  6:18                   ` Lele Gaifax
2019-04-02 17:09       ` Stefan Monnier
2019-04-02 17:57         ` Drew Adams [this message]

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=f69229de-9013-4c5e-a692-7c11718721fb@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
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).