Set doom--initial-load-path in sandbox

Prevents loaded packages miscount (e.g. -1) in dashboard/log in sandbox
instance.

This occurs because the benchmark line uses a simple heuristic to
determine the loaded packages: length of load-path minus the length of
doom--initial-load-path (to save on more expensive counting methods).
However, in the sandbox, load-path is pre-populated with all packages
right from the get-go, so doom--initial-load-path will be incorrect.
This commit is contained in:
Henrik Lissner 2020-10-26 05:51:43 -04:00
parent 9e1ac0c0be
commit fe37a590cc
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395

View file

@ -317,6 +317,7 @@ Some items are not supported by the `nsm.el' module."
process-environment ',doom--initial-process-environment process-environment ',doom--initial-process-environment
exec-path ',doom--initial-exec-path exec-path ',doom--initial-exec-path
init-file-debug t init-file-debug t
doom--initial-load-path load-path
load-path ',load-path load-path ',load-path
package--init-file-ensured t package--init-file-ensured t
package-user-dir ,package-user-dir package-user-dir ,package-user-dir