Skip to content
This repository has been archived by the owner on Apr 16, 2024. It is now read-only.

Idiomatic way to version control (dotfiling) doom configs? #79

Closed
starptr opened this issue Aug 3, 2021 · 6 comments
Closed

Idiomatic way to version control (dotfiling) doom configs? #79

starptr opened this issue Aug 3, 2021 · 6 comments
Labels
scope: enhancement New feature or request
Milestone

Comments

@starptr
Copy link

starptr commented Aug 3, 2021

Since ~/.config/doom-nvim/ is a git repo with this github repo as the remote, it's not trivial to add the doomrc.lua, doom_config.lua, and plugins.lua files to a dotfiles manager like yadm.

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).

@kaii-zen
Copy link

kaii-zen commented Aug 4, 2021

Doom Emacs does this by keeping itself in ~/.config/emacs and loading the user config from ~/.config/doom which the user can decide whether they want to version control or not...

@starptr
Copy link
Author

starptr commented Aug 4, 2021

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 :)

@NTBBloodbath
Copy link
Collaborator

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 doom-nvim installed (now it's installed in ~/.config/nvim by default instead of a custom path) so maybe we can use the same structure as Doom Emacs (~/.config/nvim for keeping doom-nvim and ~/.config/doom-nvim for keeping the user configurations).

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 doom-nvim configurations in two paths depending on your needs:

  1. The default path (~/.config/nvim)
  2. A custom path (~/.config/doom-nvim by default)

Let me know what do you think about so we can implement it soon.

Regards

@NTBBloodbath NTBBloodbath added this to the 3.1.0 milestone Aug 4, 2021
@NTBBloodbath NTBBloodbath added the scope: enhancement New feature or request label Aug 4, 2021
@NTBBloodbath
Copy link
Collaborator

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)

@starptr
Copy link
Author

starptr commented Aug 5, 2021

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)

@NTBBloodbath
Copy link
Collaborator

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
scope: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants