Better way of handling configuration #395
-
How is the best way to handle custom config? I saw in an issue that I could put the config files in a folder separate from the distribution, like how Doom-Emacs work, but could not find that in the documentation. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hey, Seems like we didn't port all of our previous documentation files to the new Doom version (and I gotta fix that, my apologies!). However, you can take a look at the old FAQ here as it does have a section about this. There's also this small code chunk that tells you what directory is used by Doom-Nvim to look for your custom configuration files (and you can also tweak it to point to elsewhere you wish and should work as expected). tl;drDoom-Nvim follows the same conventions as Doom-Emacs to handle custom config by default, that means, Doom-Emacs does make use of You can store |
Beta Was this translation helpful? Give feedback.
Hey,
Seems like we didn't port all of our previous documentation files to the new Doom version (and I gotta fix that, my apologies!). However, you can take a look at the old FAQ here as it does have a section about this.
There's also this small code chunk that tells you what directory is used by Doom-Nvim to look for your custom configuration files (and you can also tweak it to point to elsewhere you wish and should work as expected).
tl;dr
Doom-Nvim follows the same conventions as Doom-Emacs to handle custom config by default, that means, Doom-Emacs does make use of
~/.config/doom
directory to store user configurations and Doom-Nvim does make use of~/.config/doom-nvim
directory for that…