2b98e550e8
Originally, I built the load-path with site-lisp paths first, then packages. There was a modest ~10% startup boost doing this, because there were considerably more site packages loaded at startup than plugins. However, this meant built-in packages would get precedence over plugins, which is undesirable. In org's case, I simply modified the load-path in lang/org/init.el. However, this issue has cropped up again in #340. Evidently, that 10% boost may not be worth the risk it imposes, so I've rearranged the load-path with packages first. |
||
---|---|---|
.. | ||
autoload | ||
test | ||
core-editor.el | ||
core-keybinds.el | ||
core-lib.el | ||
core-os.el | ||
core-packages.el | ||
core-projects.el | ||
core-ui.el | ||
core.el | ||
packages.el |