Preferred way to keep personal configs on git with minimal-emacs.d? #13
-
Hey, thanks for the great config! This is exactly what I was looking for to start building my own Emacs config. No need to write tons of config just to get the editor barely usable but not too much going on either. I'm curious what is the preferred way to keep my own configs ( Now I did it with symbolic links and making a new separate git repository that only holds my personal configs. Is this okay or can I run into issues down the line? Better to fork and remove the ignored files from .gitignore? Or both work ok? Newish to version control and git! Could the absolutely excellent README also have small section about this topic? (below is what I'm doing right now)
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hello @jhiltu, I am glad to hear the The symbolic link solution you're using is actually a solid approach. It keeps the configuration separate while still allowing you to easily pull updates from the original repository. Alternative solution: Modify the (setq minimal-emacs-user-directory "~/.config/min-emacs/") This will ensure that the |
Beta Was this translation helpful? Give feedback.
Hello @jhiltu,
I am glad to hear the
minimal-emacs.d
config has been helpful to you!The symbolic link solution you're using is actually a solid approach. It keeps the configuration separate while still allowing you to easily pull updates from the original repository.
Alternative solution: Modify the
minimal-emacs-user-directory
variable by adding the following to the~/.emacs.d/pre-early-init.el
file:This will ensure that the
minimal-emacs.d
configuration loadspost-early-init.el
,pre-init.el
, andpost-init.el
from~/.config/min-emacs/
.