Add a short note to the elpaca section
This commit is contained in:
parent
f8b1119e83
commit
42afc8b73f
2 changed files with 31 additions and 46 deletions
|
@ -43,25 +43,6 @@ be updated accordingly.
|
|||
|
||||
#+toc: headlines 2
|
||||
|
||||
Here is what the generated directory structure should look like:
|
||||
|
||||
#+begin_src sh :dir ~/src/prototypes/emacs-up :results raw
|
||||
fd -e el -e org -E elpa | tree --fromfile
|
||||
#+end_src
|
||||
|
||||
#+RESULTS:
|
||||
.
|
||||
├── early-init.el
|
||||
├── init.el
|
||||
├── unravel-emacs.org
|
||||
└── unravel-modules
|
||||
├── unravel-completion.el
|
||||
├── unravel-essentials.el
|
||||
├── unravel-langs.el
|
||||
└── unravel-theme.el
|
||||
|
||||
2 directories, 7 files
|
||||
|
||||
To make a change to this Emacs configuration, edit this file and then type =C-c C-v C-t= (=M-x org-babel-tangle=) to republish all the relevant files.
|
||||
|
||||
* The =early-init.el= file
|
||||
|
@ -307,6 +288,10 @@ package archives, pinning packages, and setting priorities:
|
|||
:CREATED: [2024-12-10 Tue 14:43]
|
||||
:END:
|
||||
|
||||
I use ~elpaca~ for package management, and ~use-package~ for configuration management. This means that ~elpaca~ replaces the built-in ~package.el~ functionality.
|
||||
|
||||
I do it this way because it simplifies my developement workflow for the emacs-lisp packages I want to contribute to. The built-in ~package.el~ is just fine, and if you prefer that, you should just COMMENT this section, uncomment [[#h:424340cc-f3d7-4083-93c9-d852d40dfd40][The =init.el= settings for packages (=package.el=)]] and re-export all the code-blocks.
|
||||
|
||||
#+begin_src emacs-lisp :tangle "init.el"
|
||||
;;; Install Elpaca
|
||||
|
||||
|
@ -4771,8 +4756,8 @@ Note that demanding ~eglot~ is not a mistake. I want it loaded so that I can adv
|
|||
;;;; Eglot (built-in client for the language server protocol)
|
||||
(use-package eglot
|
||||
:ensure nil
|
||||
:demand t ; Not a mistake, we need to load Eglot elisp code before
|
||||
; we open any Python file.
|
||||
:demand t ;; Not a mistake, we need to load Eglot elisp code before
|
||||
;; we open any Python file.
|
||||
:functions (eglot-ensure)
|
||||
:commands (eglot)
|
||||
:bind
|
||||
|
|
|
@ -28,8 +28,8 @@
|
|||
;;;; Eglot (built-in client for the language server protocol)
|
||||
(use-package eglot
|
||||
:ensure nil
|
||||
:demand t ; Not a mistake, we need to load Eglot elisp code before
|
||||
; we open any Python file.
|
||||
:demand t ;; Not a mistake, we need to load Eglot elisp code before
|
||||
;; we open any Python file.
|
||||
:functions (eglot-ensure)
|
||||
:commands (eglot)
|
||||
:bind
|
||||
|
|
Loading…
Reference in a new issue