From: Eli Zaretskii <eliz@gnu.org>
To: Radon Rosborough <radon.neon@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Fix `early-init-file' value when file is missing
Date: Wed, 13 Feb 2019 19:56:59 +0200 [thread overview]
Message-ID: <83zhqzo9lg.fsf@gnu.org> (raw)
In-Reply-To: <CADB4rJGm6ROrJMx-0U3Z=E2TvZUqFTCNuAU6Qw+qVaVrDerxYA@mail.gmail.com> (message from Radon Rosborough on Tue, 12 Feb 2019 18:36:20 -0800)
> From: Radon Rosborough <radon.neon@gmail.com>
> Date: Tue, 12 Feb 2019 18:36:20 -0800
> Cc: emacs-devel <emacs-devel@gnu.org>
>
> > if you can come up with such a safe change, I will of course gladly
> > accept it.
>
> It is attached.
Thanks. This still uses the indirect evidence of the second function
argument.
Maybe all of this will be much simpler if in this fragment:
;; Load the early init file, if found.
(load-user-init-file
(lambda ()
(expand-file-name
"early-init"
(file-name-as-directory
(concat "~" init-file-user "/.emacs.d")))))
we replace "early-init" with "early-init.el"? Does that solve the
problem? If so, do you see any downsides with such a change? We
didn't advertise the support for "~/.emacs.d/early-init", with no
extension.
WDYT?
next prev parent reply other threads:[~2019-02-13 17:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 5:54 [PATCH] Fix `early-init-file' value when file is missing Radon Rosborough
2019-01-23 3:47 ` Radon Rosborough
2019-01-29 17:24 ` Radon Rosborough
2019-01-29 17:46 ` Eli Zaretskii
2019-02-01 9:11 ` Eli Zaretskii
2019-02-01 23:10 ` Radon Rosborough
2019-02-08 7:32 ` Eli Zaretskii
2019-02-08 17:34 ` Radon Rosborough
2019-02-08 21:52 ` Eli Zaretskii
2019-02-10 23:04 ` Radon Rosborough
2019-02-10 23:14 ` Stefan Monnier
2019-02-11 16:05 ` Eli Zaretskii
2019-02-12 5:38 ` Radon Rosborough
2019-02-12 16:14 ` Eli Zaretskii
2019-02-13 2:36 ` Radon Rosborough
2019-02-13 17:56 ` Eli Zaretskii [this message]
2019-02-16 0:47 ` Radon Rosborough
2019-02-16 7:17 ` Eli Zaretskii
2019-02-16 20:26 ` Radon Rosborough
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=83zhqzo9lg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=radon.neon@gmail.com \
/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.