Clarify description of general structure

This commit is contained in:
Daniel - 2019-12-20 17:19:35 +01:00
parent 96fd57bb90
commit d52ee6698c
No known key found for this signature in database
GPG Key ID: 1C7071A75BB72D64
1 changed files with 6 additions and 8 deletions

View File

@ -78,16 +78,14 @@ work nevertheless, even without these private files.
The main =init.el= file consists mostly of variable assignments, =use-package= The main =init.el= file consists mostly of variable assignments, =use-package=
declarations, initializing the =package= subsystem, and loading customizations. declarations, initializing the =package= subsystem, and loading customizations.
The main lifting is done by the =db/run-init= function, which is attached to the The main lifting is done by the =db/run-init= function, which is attached to
=after-init-hook= in =init.el=. This way, all necessary local hooks and =after-init-hook= in =init.el=. This way, all necessary local hooks and
autoloads are set up by =init.el=, and the =db/run-init= functions only autoloads are set up by =init.el=, and the =db/run-init= functions only
activates a (minimal?) configurations needed for every session, including activates modes needed for every session, sets default keybindings, hydras, and
modes, keybindings, hydras, and global hooks. It also imports some environment global hooks. It also imports some environment variables and starts the server.
variables and starts the server when running under windows. Any additional Any additional packages are only loaded when required. Additionally, after all
packages are only loaded when required. this, ~db/run-init~ loads all files contained in ~db/after-init-load-files~, in
the order given in that list.
Lastly, ~db/run-init~ loads all files contained in ~db/after-init-load-files~,
in that order.
* Known Limitations * Known Limitations