You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2024. It is now read-only.
What is the feature, what would you like to be able to do?
Experiencing how doom-nvim is managed, I thought we should change the default doom-nvim installation structure to something similar to LunarVim's approach.
The approach they've chosen is similar to how doom-emacs operates, the LunarVim files are placed inside ~/.config/lvim wheras the user configuration files are placed inside ~/.config/nvim.
What is the use case, why do you want this feature?
Easier to manage your doom-nvim configuration files without messing up doom-nvim -> reduces the amount of files one is allowed to tinker with + enable us to easily manage separate config files for our custom plugin list without overcrowding doom-dir.
Easier to automate the installation of doom-nvim & the placement of your personal configuration files inside ~/.config/nvim.
Ease of grepping the sought after code-lines when dealing with the user-config files.
What can also be done is renaming doom files to config.lua, modules.lua and plugins.lua instead of the doom-filename which doom-nvim is currently using.
The text was updated successfully, but these errors were encountered:
This is actually doable, doom configuration files can be placed under ~/.config/doom-nvim directory like Doom Emacs (we added a -nvim to not cause problems with doom emacs if it's installed).
What can also be done is renaming doom files to config.lua, modules.lua and plugins.lua instead of the doom-filename which doom-nvim is currently using.
Sounds good to me and this is going to be made in the new modules architecture PR that we are going to merge soon I hope.
This is actually doable, doom configuration files can be placed under ~/.config/doom-nvim directory like Doom Emacs (we added a -nvim to not cause problems with doom emacs if it's installed).
Generating a doom-nvim and placing the config files in ~/.config/doom-nvim is more appropriate than having them placed in ~/.config/nvim in my opinion.
Another thing that would be wonderful to have is the ability to create config files inside a specified folder for the sake of maintaining a better config structure in general. And by this I mean, being able to keep plugin configuration files in a separate folder inside ~/.config/doom-nvim. (maybe, ~/.config/doom-nvim/settings or something?)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the feature, what would you like to be able to do?
Experiencing how doom-nvim is managed, I thought we should change the default doom-nvim installation structure to something similar to LunarVim's approach.
The approach they've chosen is similar to how doom-emacs operates, the LunarVim files are placed inside
~/.config/lvim
wheras the user configuration files are placed inside~/.config/nvim
.What is the use case, why do you want this feature?
~/.config/nvim
.Possible Implementation (if applicable)
LunarVim's approach.
Additional context
What can also be done is renaming doom files to
config.lua
,modules.lua
andplugins.lua
instead of thedoom-filename
which doom-nvim is currently using.The text was updated successfully, but these errors were encountered: