Where to put private pre init configs about castlemacs HOT 4 CLOSED

Hi,

Since we have init.el + private.el, I guess we should have early-init.el + early-init-private.el. What do you think?

from castlemacs.

In my case, I use .emacs that is a traditional way.
For example, I put some settings and loading init.el explicitly in my .emacs.

;; pur your setting for benchmarking settings before loading init.el
(defconst my-profiler-p nil
  "If non-nil, use built-in profiler.el.")
(when my-profiler-p
  (profiler-start 'cpu+mem))
(setq custom-file (expand-file-name "custom.el" user-emacs-directory))

;; load init.el
(load "~/Dropbox/emacs.d/config/init.el" nil t)

;; report profile result if my-profiler-p is non-nil
(when my-profiler-p
    (profiler-report))

from castlemacs.

Hi,

Since we have init.el + private.el, I guess we should have early-init.el + early-init-private.el. What do you think?

Yeah I like the semantics of early-init-private.el.

It probably should come with a caveat in the README that no package specific settings can be included in that file since use-package would probably not have been bootstraped yet when it is processed?

from castlemacs.

Yes, you're right. It's time to include a whole section on both private config files. I'll work on this later this week.

from castlemacs.