-
-
Notifications
You must be signed in to change notification settings - Fork 107
Idiomatic way to version control (dotfiling) doom configs? #79
Comments
Doom Emacs does this by keeping itself in |
Right. It would be awesome if doom nvim can also implement a similar config structure such that doom itself and user configs are located separately, so that dotfile managers can play nicely with the user configs :) |
Hey, I'm pretty sure that it's gonna be useful also I don't like the submodules idea. Actually there are a lot of changes in the development version regarding to where is But I don't want to make the source too complex or keeping introducing breaking changes so we can make this a feature so you will be able to keep your
Let me know what do you think about so we can implement it soon. Regards |
Hey, so I just pushed a few changes to implement it the way I said before and also added an entry to our FAQ (I'm thinking about moving it to a wiki entry when 3.1 is released as a stable version) |
That sounds great, my setup is currently too wonky to try it out the dev branch but it looks nice & clean (and proven based on doom emacs) |
I'll be closing this because the feature was already implemented in the development version so I can have a better track of the next version milestone 🙂 Feel free to reopen this in the future if you're still facing issues while dotfiling doom-nvim |
Since
~/.config/doom-nvim/
is a git repo with this github repo as the remote, it's not trivial to add thedoomrc.lua
,doom_config.lua
, andplugins.lua
files to a dotfiles manager likeyadm
.Is there a recommended way to do this? I was thinking that maybe one could fork the repo & add the fork as a submodule to yadm, but that's not a very clean solution (updates won't work without syncing the fork) (and for me personally I'd rather avoid submodules).
The text was updated successfully, but these errors were encountered: