doomemacs/lisp
Henrik Lissner 55736ac2a6
fix(lib): prevent autoload failure at startup
In some edge cases, an early call to doom-log will cause an autoload
error because of one or more of the following is true:

- The autoloads file hasn't been generated or loaded,
- The autoloads file is out of date (especially relevant after
  b9933e6),
- doom-cli hasn't loaded lib/files eagerly yet.

To avoid this, and due to how prolific doom-log's uses are, and how
trivial the dependency is, I simply remove the dependency.

Amend: b9933e6637
2022-07-31 13:31:21 +02:00
..
cli fix(cli): more future resistant 'doom upgrade' 2022-07-31 00:58:36 +02:00
lib fix(lib): prevent autoload failure at startup 2022-07-31 13:31:21 +02:00
doom-cli-lib.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-cli.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-editor.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-keybinds.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-lib.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-modules.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-packages.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-projects.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-start.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom-ui.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
doom.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00
packages.el refactor!: restructure Doom core 2022-07-30 22:41:13 +02:00