@ -6,7 +6,7 @@ The core workings of the doom-nvim framework.
- `init.lua` Entrypoint
- `doom_global.lua` Sets the `doom` global object including default settings and `use_*` style helper functions.
- `config.lua` Responsible for configuring doom-nvim, will use the user's `modules.lua` and `config.lua`
- `modules.lua` Returns the user's `module.lua` file and caches it. Used by `config.lua` to determine which modules to import/configure.
- `modules.lua` Responsible for storing the enabled modules (user's `modules.lua` file) as well as later acting upon `doom.modules` to set everything up.
- `functions.lua` Extra helper functions used internally by doom-nvim.
- `commands.lua` Extra helper commands used internally by doom-nvim.
- `ui.lua` Loads the user's colorscheme from the `doom.colorscheme` field. Falls back to `doom-one` if a colorscheme isn't set or is broken.
@ -23,3 +23,7 @@ Those modules are the following:
d. Runs the user's `config.lua` file (so the user can apply their config)
e. Applies some of the settings in the `doom` global object such as `doom.indent`
3. `init.lua` loads `functions.lua` and `commands.lua` to set these extra functions/commands.
4. `init.lua` runs the `start`, `load_modules` and `handle_user_config` functions of `modules.lua` which does the following:
a. Install/bootstrap packer on behalf of the user.
b. `load_modules` will iterate over the `doom.modules` field (set in `config.lua`), installing packer dependencies, binding autocmds and regular cmds.
c. `handle_user_config` will handle the user imported packages, autocmds and vim cmds from the `use_*` functions (from user's `config.lua` file).