gitback/doomemacs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
f9c2397a3c
doomemacs/lisp/cli/profiles.el

84 lines
2.8 KiB
EmacsLisp
Raw Normal View History

fix(cli): add lisp/cli/profiles.el I forgot to add the definitions for the 'doom profile{s,}' commands in b914830, which causes "unrecognized command 'profiles sync'" errors on 'doom {sync,upgrade}'. My unparalleled brilliance is 4 parallel universes ahead of me, clearly. Amend: b91483040363
2022-09-16 08:23:42 +08:00
;;; lisp/cli/profiles.el -*- lexical-binding: t; -*-
;;; Commentary:
;;; Code:
;;
;;; Variables
(defvar doom-cli-known-profiles-file
fix(profiles): no bootstrap file for non-bootloaders If Doom doesn't live in ~/.emacs.d or ~/.config/emacs, then it cannot play the role of bootloader, so opt out of generating the profile bootstrappper in this case. That said, don't disable the profile system entirely; it can still be useful for internal, noninteractive, and sandbox use.
2022-09-17 20:50:23 +08:00
(file-name-concat doom-cache-dir (format "profiles.%s.el" (or (car doom-profile) "@")))
;; REVIEW: Use `doom-profile-data-dir' in v3
;; (file-name-concat doom-profile-data-dir "known-profiles.el")
fix(cli): add lisp/cli/profiles.el I forgot to add the definitions for the 'doom profile{s,}' commands in b914830, which causes "unrecognized command 'profiles sync'" errors on 'doom {sync,upgrade}'. My unparalleled brilliance is 4 parallel universes ahead of me, clearly. Amend: b91483040363
2022-09-16 08:23:42 +08:00
"TODO")
;;
;;; doom profile ...
(defcli-stub! ((profile pf)) ())
(defcli-stub! (profile hash) ())
(defcli-stub! (profile new) ())
(defcli-stub! (profile archive) ())
(defcli-stub! (profile (remove rm)) ())
(defcli-stub! (profile (rename mv)) ())
(defcli-stub! (profile nuke) ())
;;
;;; doom profiles ...
feat(cli): add --reload switch to 'profiles sync' So 'doom profiles sync' can be relied on to forcibly regenerate the profile init by default.
2022-09-17 19:05:06 +08:00
(defcli! (profiles sync) ((reload? ("--reload")))
fix(cli): add lisp/cli/profiles.el I forgot to add the definitions for the 'doom profile{s,}' commands in b914830, which causes "unrecognized command 'profiles sync'" errors on 'doom {sync,upgrade}'. My unparalleled brilliance is 4 parallel universes ahead of me, clearly. Amend: b91483040363
2022-09-16 08:23:42 +08:00
"Synchronize your profiles with Doom."
:benchmark t
(let* ((old-profiles (doom-profiles-read doom-cli-known-profiles-file))
(new-profiles (doom-profiles-autodetect))
feat(cli): introduce DOOMPROFILELOAD{FILE,PATH} envvars - Adds $DOOMPROFILELOADFILE: Controls where to read and write the profile loader. Changing this may be helpful for users on nix/guix, who have deployed Doom to a read-only location. This sets `doom-profile-load-file`. - Changed profile load file's default location (used to be $EMACSDIR/profiles/init.el, is now $EMACSDIR/profiles/load.el). The gitignore was updated to reflect this. - Adds $DOOMPROFILELOADPATH: A colon-delimited list of profile config files and directories (semi-colon on Windows) which dictate what Doom reads in order to discover your profiles. Config files are required to have an *.el extension. This sets `doom-profile-load-path`. - Changes the nomenclature around this loader script. I used to refer to it as the profile bootstrapper. I'll now refer to it as the profile load file, and I've renamed `doom-profiles-bootstrap-file` to `doom-profile-load-file` to reflect this. - The variables `doom-profile-dirs` and `doom-profile-config-files` were merged into doom-profile-load-path. - Both envvars have also been documented in `doom help` (and $DOOMPROFILE's has been updated). Ref: #6794
2022-09-18 04:02:50 +08:00
(load-file doom-profile-load-file)
(version (doom-file-read load-file :by 'read :noerror t))
feat(cli): add --reload switch to 'profiles sync' So 'doom profiles sync' can be relied on to forcibly regenerate the profile init by default.
2022-09-17 19:05:06 +08:00
(recreate? (or (not reload?) (doom-profiles-outdated-p))))
feat(cli): introduce DOOMPROFILELOAD{FILE,PATH} envvars - Adds $DOOMPROFILELOADFILE: Controls where to read and write the profile loader. Changing this may be helpful for users on nix/guix, who have deployed Doom to a read-only location. This sets `doom-profile-load-file`. - Changed profile load file's default location (used to be $EMACSDIR/profiles/init.el, is now $EMACSDIR/profiles/load.el). The gitignore was updated to reflect this. - Adds $DOOMPROFILELOADPATH: A colon-delimited list of profile config files and directories (semi-colon on Windows) which dictate what Doom reads in order to discover your profiles. Config files are required to have an *.el extension. This sets `doom-profile-load-path`. - Changes the nomenclature around this loader script. I used to refer to it as the profile bootstrapper. I'll now refer to it as the profile load file, and I've renamed `doom-profiles-bootstrap-file` to `doom-profile-load-file` to reflect this. - The variables `doom-profile-dirs` and `doom-profile-config-files` were merged into doom-profile-load-path. - Both envvars have also been documented in `doom help` (and $DOOMPROFILE's has been updated). Ref: #6794
2022-09-18 04:02:50 +08:00
(unless (file-exists-p load-file)
(print! (warn "No profile loader found. Generating one..."))
fix(cli): add lisp/cli/profiles.el I forgot to add the definitions for the 'doom profile{s,}' commands in b914830, which causes "unrecognized command 'profiles sync'" errors on 'doom {sync,upgrade}'. My unparalleled brilliance is 4 parallel universes ahead of me, clearly. Amend: b91483040363
2022-09-16 08:23:42 +08:00
(print-group! (print! (start "Regenerating it...")))
(setq recreate? t))
(unless (equal (or version doom-version) doom-version)
feat(cli): introduce DOOMPROFILELOAD{FILE,PATH} envvars - Adds $DOOMPROFILELOADFILE: Controls where to read and write the profile loader. Changing this may be helpful for users on nix/guix, who have deployed Doom to a read-only location. This sets `doom-profile-load-file`. - Changed profile load file's default location (used to be $EMACSDIR/profiles/init.el, is now $EMACSDIR/profiles/load.el). The gitignore was updated to reflect this. - Adds $DOOMPROFILELOADPATH: A colon-delimited list of profile config files and directories (semi-colon on Windows) which dictate what Doom reads in order to discover your profiles. Config files are required to have an *.el extension. This sets `doom-profile-load-path`. - Changes the nomenclature around this loader script. I used to refer to it as the profile bootstrapper. I'll now refer to it as the profile load file, and I've renamed `doom-profiles-bootstrap-file` to `doom-profile-load-file` to reflect this. - The variables `doom-profile-dirs` and `doom-profile-config-files` were merged into doom-profile-load-path. - Both envvars have also been documented in `doom help` (and $DOOMPROFILE's has been updated). Ref: #6794
2022-09-18 04:02:50 +08:00
(print! (warn "Detected version mismatch in profile loader (%s != %s)"
version doom-version))
fix(cli): add lisp/cli/profiles.el I forgot to add the definitions for the 'doom profile{s,}' commands in b914830, which causes "unrecognized command 'profiles sync'" errors on 'doom {sync,upgrade}'. My unparalleled brilliance is 4 parallel universes ahead of me, clearly. Amend: b91483040363
2022-09-16 08:23:42 +08:00
(print! (start "Generating profile manifest..."))
(setq recreate? t))
(print-group!
(if (not recreate?)
(doom-log "Profiles are up-to-date!")
(let* ((pred (lambda (a b) (eq (car a) (car b))))
(added (seq-difference new-profiles old-profiles pred))
(removed (seq-difference old-profiles new-profiles pred))
(changed (cl-loop for profile in (seq-intersection new-profiles old-profiles pred)
unless (equal (cdr profile)
(alist-get (car profile) old-profiles))
collect profile)))
(when (or added removed changed recreate?)
(print! (start "Synchronizing %d known profile%s...")
(length new-profiles)
(if (/= (length new-profiles) 1) "s" ""))
(print-group!
(dolist (p added) (print! (item "Added %S") (car p)))
(dolist (p removed) (print! (item "Removed %S") (car p)))
(dolist (p changed) (print! (item "Changed %S") (car p)))
(doom-file-write doom-cli-known-profiles-file (list new-profiles) :mode #o600)
feat(cli): introduce DOOMPROFILELOAD{FILE,PATH} envvars - Adds $DOOMPROFILELOADFILE: Controls where to read and write the profile loader. Changing this may be helpful for users on nix/guix, who have deployed Doom to a read-only location. This sets `doom-profile-load-file`. - Changed profile load file's default location (used to be $EMACSDIR/profiles/init.el, is now $EMACSDIR/profiles/load.el). The gitignore was updated to reflect this. - Adds $DOOMPROFILELOADPATH: A colon-delimited list of profile config files and directories (semi-colon on Windows) which dictate what Doom reads in order to discover your profiles. Config files are required to have an *.el extension. This sets `doom-profile-load-path`. - Changes the nomenclature around this loader script. I used to refer to it as the profile bootstrapper. I'll now refer to it as the profile load file, and I've renamed `doom-profiles-bootstrap-file` to `doom-profile-load-file` to reflect this. - The variables `doom-profile-dirs` and `doom-profile-config-files` were merged into doom-profile-load-path. - Both envvars have also been documented in `doom help` (and $DOOMPROFILE's has been updated). Ref: #6794
2022-09-18 04:02:50 +08:00
(doom-profiles-save new-profiles load-file)
(print! (success "Regenerated profile loader: %s")
(path load-file)))))))))
fix(cli): add lisp/cli/profiles.el I forgot to add the definitions for the 'doom profile{s,}' commands in b914830, which causes "unrecognized command 'profiles sync'" errors on 'doom {sync,upgrade}'. My unparalleled brilliance is 4 parallel universes ahead of me, clearly. Amend: b91483040363
2022-09-16 08:23:42 +08:00
;;
;;; Helpers
(provide 'doom-cli-profiles)
;;; profiles.el ends here
Reference in New Issue Copy Permalink