refactor(lib): provide doom-libs as subfeatures
This allows us to load them via doom-require. Why not use normal features? Because Doom's libraries are designed to be loaded as part of Doom, and will openly rely on Doom state if needed; this is a contract I want to enforce by ensuring their only entry points are through `doom-require` or autoloading. I will add them to the rest of the libraries later. Site-node: this also adds Commentary+Code to the comment headings, as I want a space to use that space to describe the library, when I get around to it.
This commit is contained in:
parent
a179b8d262
commit
b121c5e1c6
8 changed files with 57 additions and 20 deletions
|
@ -1,4 +1,6 @@
|
|||
;;; lisp/lib/process.el -*- lexical-binding: t; -*-
|
||||
;;; Commentary:
|
||||
;;; Code:
|
||||
|
||||
;;;###autoload
|
||||
(defun doom-call-process (command &rest args)
|
||||
|
@ -40,3 +42,6 @@ Warning: freezes indefinitely on any stdin prompt."
|
|||
(sit-for 0.1))
|
||||
(process-exit-status process))
|
||||
(string-trim (buffer-string)))))
|
||||
|
||||
(provide 'doom-lib '(process))
|
||||
;;; process.el ends here
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue