all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Settings
Date: Tue, 27 Aug 2019 09:20:51 +0300	[thread overview]
Message-ID: <83zhjvdt8c.fsf@gnu.org> (raw)
In-Reply-To: <E1i2OB0-0002AP-G5@fencepost.gnu.org> (message from Richard Stallman on Mon, 26 Aug 2019 19:13:30 -0400)

> From: Richard Stallman <rms@gnu.org>
> Date: Mon, 26 Aug 2019 19:13:30 -0400
> Cc: larsi@gnus.org, emacs-devel@gnu.org
> 
>   > IOW if Emacs just loads ~/.emacs.d/custom.el before ~/.emacs.d/emacs.el
>   > some things will break, and same thing if it swaps the order.
> 
> I wonder if we can do something more intelligent about this.
> For instance, can we figure out that certain variables need to be set early
> and others late?

What is "early" and what is "late" depends on the order of user
customizations in .emacs, which is entirely out of our control, and
can be almost arbitrary.

We introduced the early-init file in Emacs 27 to let users themselves
control which customizations are done early and which later, because
some customizations should be in place before we read .emacs.



      parent reply	other threads:[~2019-08-27  6:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 21:52 Settings Lars Ingebrigtsen
2019-08-15 23:11 ` Settings Drew Adams
2019-08-25 15:45 ` Settings Stefan Monnier
2019-08-25 16:30   ` Settings Drew Adams
2019-08-25 18:21     ` Settings Stefan Monnier
2019-08-26  4:18   ` Settings Lars Ingebrigtsen
2019-08-26 23:13   ` Settings Richard Stallman
2019-08-26 23:20     ` Settings Drew Adams
2019-08-27 23:22       ` Settings Richard Stallman
2019-08-30  9:50         ` Settings Lars Ingebrigtsen
2019-08-31  2:54           ` Settings Richard Stallman
2019-08-27  6:20     ` Eli Zaretskii [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zhjvdt8c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.