split .spacemacs file into components?

[kevinushey]

Just some feedback + a suggestion re: updating to the new Spacemacs release...

One bit that was a little bit painful for me was updating my .spacemacs file to ensure that I inherited the new defaults for the latest Spacemacs release. Because I had a bunch of code inline in my .spacemacs file for user configuration, I had to manually copy that out, remove the .spacemacs file, ask Spacemacs to re-generate my .spacemacs file, and then copy that code back in.

I wonder if this process could be made a little bit simpler? My proposal: the default implementations for dotspacemacs/user-config and dotspacemacs/user-init could be tweaked to have a default of e.g.

(defun dotspacemacs/user-init ()
 (if (file-readable-p "~/.emacs.d/user-init.el") (load "~/.emacs.d/user-init.el")))

This way, users could provide their own config in separate files, ~/.emacs.d/user-init.el, and more easily update their .spacemacs file as the distributed copy / defaults change.

Some other candidates for places to look for init files:

• ~/.emacs.d/user-init.el
• ~/.emacs.d/spacemacs-user-init.el
• ~/.spacemacs.user-init

Thanks!

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!