memory-leaks

commit f6753e0d886e540b48eff8b6f4be7c51a2b49d01
parent 7d580cd6bf25f1f81761b099aa0fc8f5669f7f49
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Sun, 26 Mar 2023 22:57:57 +0200

Jot down more notes re. hacking on forge

Diffstat:
M
guides/emacs/development.org
 | 
15
+++++++++++++++

1 file changed, 15 insertions(+), 0 deletions(-)
diff --git a/guides/emacs/development.org b/guides/emacs/development.org
@@ -92,3 +92,18 @@ elpa_dirs = $(foreach d,$(elpa),$(call find-lib,$(d)))
 LOAD_PATH = $(addprefix -L ,$(elpa_dirs) $(sources))
 #+end_src
 
+*** load sources
+~emacs -Q -L ./lisp~ does not seem to work: after running
+~(package-initialize)~, =M-x find-library forge= returns the instance
+installed under ~package-user-dir~.
+
+This can be circumvented with ~(setq pacakge-load-list '((forge nil)
+all))~.
+
+Full command line for easy startup:
+
+#+begin_src sh
+emacs -Q -L ./lisp \
+      -eval "(setq pacakge-load-list '((forge nil) all))" \
+      -f package-initialize \
+#+end_src